MySQL Bugs: #33751: Addition note to problem with ODBC listed in (26.1.6.3.6)

Bug #33751	Addition note to problem with ODBC listed in (26.1.6.3.6)
Submitted:	8 Jan 2008 20:05	Modified:	29 May 2013 11:13
Reporter:	Isaac Tewolde	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	3.51.12	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	#Deleted# errors on insert

Description:
When inserting a new row in a table. The "#Deleted#" problem appears if there are no columns with datatypes such as INT, VARCHAR(<100), DATETIME, TIMESTAMP which have values. The instant one of these types has a value in the row being inserted then the problem disappears.

I think this may be related to the BIGINT problem mentioned. Putting values in TEXT and big VARCHAR columns(i.e varchar(300+) types) will not prevent the #DELETED# problem. However if any of the smaller data types get a value, the row is inserted without a problem.

How to repeat:
-Create a table with a primary key(int type with autoincrement), a timestamp field and the rest being either text or big varchars and a small column type (either an int, datetime, varchar(50) and so on)
-Link it into access via odbc.
-Attempt to insert a new row by putting values in any of the "big" columns
-#Deleted# problem will appear
-Put values in the "small" columns and the row is inserted without problem.

Isaac, 

the problem with auto_increment int fields has been fixed since MyODBC version 3.51.14. Therefore I would recommend you upgrading to something newer than 3.51.12. MyODBC 3.51.23 is currently available from the following page:

http://dev.mysql.com/downloads/connector/odbc/3.51.html

In case the problem still exists even after upgrade this must be something different than int auto_increment and I will request more details about the case (such as the table dump and versions of MDAC, msjet40.dll, etc).

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.