Bug #60994 LONGTEXT Does not convert properly to MEMO field in access 97 with MyODBC
Submitted: 28 Apr 2011 16:26 Modified: 14 Nov 2012 9:45
Reporter: Bryan Freedman Email Updates:
Status: Unsupported Impact on me:
None 
Category:Connector / ODBC Severity:S1 (Critical)
Version:5.1 (driver denoted 5.01.08) OS:Windows (Windows server 2003)
Assigned to: CPU Architecture:Any

[28 Apr 2011 16:26] Bryan Freedman
Description:
This is a re-report of Bug #51548, because it is still present.  The original report is correct, but the but is not fixed.  A LONGTEXT field should map to a MEMO field, not a text field which is limited to <=255 characters.  Version 3.51 of ODBC does this correctly but cannot be used because of many other bug issues.  

How to repeat:
Per original bug report, recreate as follows:
- create a table with VARCHAR > 255
- create a MyODBC 5.x DSN
- open access 97 and link the above table using the above DSN
- look at the table structure
you will see that the column is mapped to text.

I would add:

you can see that 3.51 does it correctly by doing:
-create a MyODBC 3.51 DSN
-open access 97 and link the above table using the 3.51 DSN
-look at the table structure
you will see that the column is mapped to MEMO
[28 Apr 2011 18:07] MySQL Verification Team
Thank you for the bug report. Then is duplicate of mentioned bug: http://bugs.mysql.com/bug.php?id=51548 ?. Thanks.
[28 Apr 2011 19:31] Lawrenty Novitsky
Bryan, no, that bug is not "suspended". it is still open.
[19 May 2011 12:33] Jim Leach
Is this being worked on?  http://bugs.mysql.com/bug.php?id=51548  clearly says it has been suspended.  This is a big deal to me and I need a solution.  I can duplicate this error repeatedly.  Thanks.
[14 Nov 2012 9:45] Bogdan Degtyariov
Access 97 is not supported anymore by Microsoft and we recommend upgrading it to something newer, which is proven to work such as Access 2007.
[14 Nov 2012 9:45] Bogdan Degtyariov
It was decided not to support Access 97 in any MySQL products.