Search results

just an additional information: we have also 2 front-ends on different servers in US and Europe. Christof.

We have a database to track errors during testing. The database has MS Access front-end and SQL server back-end. The project team is located in Europe and US. To increase access performance for the US team we want to replicate the back-end database to an US server. The main table containing...

Pat, still no progress - "Break on all errors" is set - all "on error" statements are commented out - all "DoCmd.SetWarnings" are commented out -> no change. Error does not pop up. - just turn on error before the docmd.close -> no change. Error does not pop up. So, still the same problem

I changed the setting to "Break on all errors" ... but no change!! :mad:

Pat, I turned off all error handlers by commenting out all ON ERROR GOTO statements and still the error message is only showing up in Trace/Debug mode. Are there any other ways to define error handlers?

The code is as follows DoCmd.SetWarnings True DoCmd.Close and after the DoCmd.Close we get the following error message ODBC--call failed [Microsoft][ODBC SQL Server Driver] Datefield overflow (#0) Hope this helps.

Really no idea out there to overcome this problem?

Interesting. We have a DoCmd.SetWarnings True in the save code. In debug mode I get the error message (ODBC failed), but not in normal mode. Any ideas? Christof.

There seems to be a misunderstanding. No error really pops up (and therefore no error message). So what's the trick to not suppress the error messages. We open a form where the user can enter his data. Pressing a SAVE button triggers DoCmd.Close That's all. Christof.

We are using a form to update a table which is on a SQL-server. Sometime it happens that the record is not updated, but we don't see an error message (e.g. set a date to 31.12.2100) How can we capture those errors? Christof.

Solved Problem was related to a BIT1 field. After conversion to CHAR 1 it works fine. Christof.

We moved the backend of an MS Access app from Access to SQL-Server. Now we see the following behaviour - We can create new records - We can update old records - We CANNOT update new records: We get the famous WriteConflict message with "Save Record" greyed out. Any explanation for this...

OK - works now - Problem was in a complete other area. Thx.

We migrated a database using autonumber fields from Access to SQL-Server. After a while we detected the IDENTIFIER type. Now we have the following problem. When adding a new record in Access, the new number is provided as soon as the first field is entered. In SQL the record behaves different...