vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On Thu, Mar 20, 2008 at 10:20 AM, Andreas <maps.on@gmx.net> wrote: > ... event before update caused an error: > Update or CancelUpdate without AddNew or Edit This sounds more like a MS-Access Visual Basic Coding problem. Any ODBC related error messages are really PostgreSQL error messages that are relayed to you. What you are describing here doesn't sound any thing like and ODBC or PostgreSQL error. They say they dont do anything special. Just clicking a checkbox or > trying to jump to the next record would do to trigger the error. > Later the same action won't cause any trouble, so I can't crack this in > debug-mode. Here on my box it always works as expected. > How are you binding the form to the user controls? Are you linking from linked tables, linked DAO recordsets, or linked ADO recordsets? Could someone here give a hint? > I would start by looking for code in the form that might be calling the form's recordset UPDATE or CancelUpdate method. Also, if this is a access problem, I would check out this site for further information: www.utteraccess.com Regards, Richard Broersma Jr. |
| |||
| Richard Broersma schrieb: > On Thu, Mar 20, 2008 at 10:20 AM, Andreas <maps.on@gmx.net > <mailto:maps.on@gmx.net>> wrote: > > > ... event before update caused an error: > Update or CancelUpdate without AddNew or Edit > > > This sounds more like a MS-Access Visual Basic Coding problem. Any > ODBC related error messages are really PostgreSQL error messages that > are relayed to you. What you are describing here doesn't sound any > thing like and ODBC or PostgreSQL error. I think it's an Access issue, too, but one that is ODBC related as I never had this problem without ODBC. I don't say it is a pgsqlODBC specific error. I hoped someone here ran into it before and knows a tweak for psqlODBC, Access or anything to improve this thing. It's not a VBA coding issue, since the whole data update is done by Access and the form that is bound to linked in tables. No ADO-, DAO recordset stuff within my code here. This form actually has a "before Update" procedure but it just inserts the current User-ID when the form was changed. This happens everytime an update occurs and works perfectly next to everytime it is called. Regards Andreas -- Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-odbc |
| ||||
| On Fri, Mar 21, 2008 at 4:49 AM, Andreas <maps.on@gmx.net> wrote: > I think it's an Access issue, too, but one that is ODBC related as I > never had this problem without ODBC. > I don't say it is a pgsqlODBC specific error. > I hoped someone here ran into it before and knows a tweak for psqlODBC, > Access or anything to improve this thing. > > This form actually has a "before Update" procedure but it just inserts > the current User-ID when the form was changed. > This happens everytime an update occurs and works perfectly next to > everytime it is called. Andreas, If you haven't solved you problem yet, you might want to following this thread to see if it provides a solution to your problem: http://www.utteraccess.com/forums/sh...Number=1616206 Regards, Richard Broersma Jr. -- Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-odbc |