I have most of the MySQL - Access integration issues solved.
- I have timestamp fields set up to autoupdate,
- I ran queries to make sure older records had a value in the timestamp field,
- and I've been scouring my code for places that I was setting a value in a field that already had that exact value.
Now my problem. If a user is on a form and checks a box, then changes their mind and unchecks it, they get a write conflict when the form closes and the data is posted to the MySQL table.
There's got to be some kind of ODBC configuration option, or some other setting in Access, that will allow this user behavior without producing the Write Conflict error message, right?