I have an application with MS Access 2000 as the front end and MySQL as the
back end. All was well until I upgraded the MySQL (Linux) server.
The Problem: I insert data into a cumulative table. Before when I did
this, and there were duplicate entries, the duplicate entries were rejected
and I got a return code with the number of affected rows (number added).
Now, I get a MyODBC error and the application stops when trying to add
duplicate entries.
3.22.27.1 - previous ver MySQL that did not return error
4.0.16.0 - current ver MySQL that returns error.
The MyODBC was not updated on the client (Windows) computer. However, I
tried updating MyODBC from ver 2.50.39 to ver 3.51.03 with no change in
results. So I am guessing that MySQL has changed what it passes to MyODBC
when it encounters this condition.
How can I set MySQL (or MyODBC or whatever) so that the insert query does
not halt the insert when it encounters a duplicate entry?
Thanks for any information.
--
Gary
To reply, remove the XXX from garyXXXlund