Bug #30997 #Deleted comes in MS Access linked table consisting of TINYTEXT field
Submitted: 13 Sep 2007 11:15 Modified: 24 Apr 2008 10:43
Reporter: Vladimir Dusa Email Updates:
Status: Verified Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51.17, 5.1.3 OS:Any
Assigned to: Bogdan Degtyariov CPU Architecture:Any
Tags: access, deleted, odbc_postga51
Triage: D4 (Minor) / R3 (Medium) / E4 (High)

[13 Sep 2007 11:15] Vladimir Dusa
Description:
#DELETED comes in the newly added row in a table consisting of three columns: 
- INTEGER (AUTO_INCREMENT), 
- TINYTEXT 
- TIMESTAMP

We are using:
MyODBC 3.51.17
MySQL 5.0.45
Windows XP Professional (SP2)
MS Access 2003 (SP2) (German version)

How to repeat:
1) Create New Table
CREATE TABLE `mytable` (
  `ID` int(10) unsigned NOT NULL auto_increment,
  `MyText` tinytext NOT NULL,
  `tmstmp` timestamp NOT NULL default CURRENT_TIMESTAMP,
  PRIMARY KEY  (`ID`)
) ENGINE=InnoDB;

2) Link this table in MS Access. We are using options "Don't Optimize Column Width" and "Return Matching Rows"

3) Try to create new row in this linked table by editing the column MyText.
=> #DELETED will appear.
[13 Sep 2007 11:37] Miguel Solorzano
Thank you for the bug report. Please test with the released version
3.51.20. Thanks in advance.
[13 Sep 2007 12:28] Vladimir Dusa
I have installed MyODBC 3.51.20, relinked the table in Access, but the problem still occurs.

We couldn't use the version 3.51.20 anyway, because the bug http://bugs.mysql.com/?id=30933 is not fixed in this version too.

Thank you

Vladimír Duša
[13 Sep 2007 15:03] Miguel Solorzano
Thank you for the feedback. Verified with Access 2003.
[9 Apr 2008 17:49] Bogdan Degtyariov
Verified in 5.1.3
[24 Apr 2008 10:10] Vladimir Dusa
Hello,

I would like to please You for solving this problem, because we still must use the MyODBC 3.51.17, which is quite old. Our application doesn't work with this problem and our new customer must use at least MyODBC 3.51.20 because of his anohter applications - it is not possible to have two MyODBC versions on one mashine. 

We will be very glad if You could help us by solving this Bug.

Thank you very much

Best regards

Vladimir Dusa
BSA Informatik AG
[24 Apr 2008 10:43] Vladimir Dusa
Sorry - this message should be added to another bug. Take it please as irrelevant.
Vladimir Dusa
[7 Dec 2010 7:34] Bogdan Degtyariov
Verified with 3.51.27 and 5.1.8 (MS Access XP and MS Access 2007)
[19 Oct 2012 8:13] Bogdan Degtyariov
Connector/ODBC 5.2.2 driver (both ANSI and Unicode versions) are affected.