Write conflict when a checkbox is changed and changed back on pop upform

[Guest]

I have a form that is bound to a linked table that links to an ODBC
connection that is connected to a MySQL installation.
The form's pop-up property is set to True. On this form I have a few
controls, among them some check boxes.
Whenever I open the form, change one of the check boxes, change it
back to what it was (checked/unchecked) and close the form I get a
write conflict.

How can I avoid this?

Steps to reproduce:
1. Create MySQL DB and create an ODBC connector to it.
2. Create an Access 2007 accdb file and create a linked table in it to
a table in the MySQL DB.
3. Create a new form, bind it to the table, set the pop-up property to
True.
4. Create a Check box on the form and bind it to a field in the table.
5. Open the form, check the check box.
6. Uncheck it, try to close the form.
7. Voila! Write conflict...

I've tried setting Me.Dirty to False, but that also causes the write
conflict.
Any ideas would be appreciated...

Thanks,
Noam Nelke, Israel.

 

[AAccess]

I had all kind of funny problems with MySQL database until I added timestamp
fields pretty much to all tables that are updated. Having just a primary key
did not do it (do not refresh to refresh the link after you add a ts field).

 

[AAccess]

Sorry, I meant to say: "do not forget to refresh the link using Linked Table
Manager"...

 

[Guest]

Thanks for the quick response...

I've tried adding a timestamp to my table. I made it update
automatically, refreshed the link, and the problem persists.

I've included steps to reproduce (it takes about a minute if you have
MySQL and the ODBC Connector set up). You can try it yourself.

I'm actually curious if it really reproduces the problem or if I have
some hidden setting that I'm missing.

Any help would be appreciated...

 

[AAccess]

Interesting. Is this an Access error message or ODBC driver's?
I'd setup odbc trace and check what commands this thing sends to the server.

In my test environment it is Access 2003 + MySQL (and it works fine).
I will try to play with Access 2007 later tonight (I was going to start
moving to 2007 anyway)