Re: Using Microsoft Access as a Front-end to MySQL

[Stephen Hubbard]

Solved the problem. Again, using XP Service Pack 3, MS Access 2007, ODBC Windows 32 bit connector Version 5.1.

On my system, using the above configuration, the key was changing the "Timestamp" column, which is needed by MySql on all tables from the "Date" data type to "Number/Double". After that, I did not need the flag set to "Return Matching Rows instead of Affected Rows" or the "Dynamic Curser" enabled. Both of these can be found on the "Details" area on Flag 1 and Flag 2 respectively. I have not tried to do anything more advanced than just modify a existing record, so these may be needed for more sophisticated work, but this did eliminate the "Write Conflict" notification and allow me to modify an existing record.