SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-17-2008, 04:27 PM
| ||||
| ||||
 Re: Access complains : Update or CancelUpdate withoutAddNew or Edit Just shooting in the dark, but do you have the Access form property 'allow additions' set to 'yes', and could a user navigate to the 'new record' without even knowing it? Perhaps they are starting a new record without knowing it, and not including information required by a record before they attempt to navigate away to another record? >>> Andreas <maps.on@gmx.net> 03/20/2008 10:20 AM >>> Hi, I've build an application with Access 2000/2003 that uses a remote PG 8.2.6 via SSH tunnel. The forms have bound controls and usually work decently. But now and then a user reports a error (I have to translate): ... event before update caused an error: Update or CancelUpdate without AddNew or Edit 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. The error appears daily so the productive folks get annoyed but I have no idea where to look.  Could someone here give a hint? -- Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-odbc -- Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-odbc      |
|
04-17-2008, 04:27 PM
| ||||
| ||||
| Re: Access complains : Update or CancelUpdate without AddNew or Edit On 3/21/08, Fred Parkinson <FredP@abag.ca.gov> wrote: > > But now and then a user reports a error (I have to translate): > .. event before update caused an error: > Update or CancelUpdate without AddNew or Edit I've only seen this error in MS-Access when I've done one of two things: I've tried up manually update or cancel an update to a record (in a recordset object) that wasn't already opened for editing or opened as a newly created record. This should be the only way that this error message should be raised. I would use the DEBUG find utility to search all of you form's code for any instances where the DAO recordset methods are being used to update your form's recordset object. I would bet that user is able to call one of these methods via the form's control's event procedures at an unexpected time when the record has not recieved any changed from the user. Regards, Richard Broersma Jr. |
 |
« " for read only" clause appended for safety when UseDeclareFetch=1 breakssome sql statements with trailing semicolons
|
PG odbc - MSQuery »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
All times are GMT. The time now is 05:39 PM.
