Write conflict

[MrMode]

I have a form bound to a MySQL linked table, the majority of fields are text fields populated on load via DLookup and there are 6 combo boxes that give the current value of the MySQL table allowing the user to make changes to the record.

This has been working without issues, however, now any changes made bring up the Write Conflict if the user tries to move to another record with Save Record greyed out...

It is not my MySQL database so I was wondering if there was anything I could check or do my end. I have a duplicate of the database that works with local tables only and there are no issues at all with the form.

I know I am being vague, but i have no idea why it is giving the user this issue all of a sudden.

Any and all help greatly appreciated.

 

[MrMode]

It could be corrupted records, I will try deleting them from the MySQL side and re inserting them to establish if something corrupted them when they were added as I cannot find anything wrong with the form construction that would cause this issue to suddenly appear when it has been working normally up until now.

I will report back.

 

[MrMode]

Sorted.

It is not my forms, or Access at all (knew as much). It is an issue between MS and MySQL. I found the answer here:

http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-errors.html

Microsoft Office and DATE or TIMESTAMP Columns
Applications in the Microsoft Office suite cannot update tables that have DATE or TIMESTAMP columns.
This is a known issue with Connector/ODBC. Ensure that the field has a default value (rather than NULL) and that the default value is nonzero (that is, something other than 0000-00-00 00:00:00).

Thanks for trying to help, it was important to check that it was not my basic grasp of coding that was the issue.

 

[dhookom]

Thanks for posting. I had heard of default values but was mostly concerned with the bit fields with no default.

Duane
Hook'D on Access
MS Access MVP