Bug #4111 The #deleted bug
Submitted: 11 Jun 2004 19:40 Modified: 18 Jun 2004 4:39
Reporter: Garrett Ives Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51 OS:
Assigned to: CPU Architecture:Any

[11 Jun 2004 19:40] Garrett Ives
Description:
When I follow the workaround for the #deleted when adding rows under MS Access 2000 (9.0.3821 SR-1) it says to "UPGRADE to Myodbc 2.0.x".  I followed all directions and noted that I was using the current production release, myodbc 3.51.  The bug did not go away.  I installed the OLD production version, 2.51 or whatever and the bug went away.  

How to repeat:
use the newer production release of the ODBC driver with microsoft access, all current updates, a primary key field, a timestamp field, no double ints, turn big ints into ints, return matching rows.

Suggested fix:
Make whatever is in 2.5 work in 3.5!
[18 Jun 2004 4:39] Miguel Solorzano
I tested with Access 2003 and following the instructions from:

http://dev.mysql.com/doc/connector/odbc/en/faq_4.html#DELETED_problem

it worked fine. Notice that the instructions for to upgrade is:

newest (version 2.6 or above) Microsoft MDAC (Microsoft Data Access Components)

isn't refering to: "UPGRADE to Myodbc 2.0.x" but instead the MDAC version
from Microsoft.