|
|
Access ODBC 'write Conflict' SOLVED!
I had this problem where a user would attempt to change a record, and always get the 'write conflict', and that another user had changed the record... even though no other users were on the database.
I searched high and low for a solution, to no avail. Yes, I had a primary key; I had a TIMESTAMP field. I played around with Access' settings for record locking, no record locking, etc.; I set the MyODBC setting to "return matching rows". None of these worked.
Here is what I found:
I had a TIMESTAMP field in the MySQL table, NULL = OK. I imported data from a text file into this table. This text file did not have the TIMESTAMP field, so all of the records in the MySQL table had a default timestamp of '00000000000000'.
I wrote a SQL statement that changed this TIMESTAMP '00000000000000' value to an arbitrary value (for example, '20030910134340'). Everything worked fine.
View Complete Forum Thread with Replies
See Related Forum Messages: Follow the Links Below to View Complete Thread
|
|
|