MySQL Bugs: #12389: Error with MyODBC with Microsoft Access 2003 (bigint fields)

Bug #12389	Error with MyODBC with Microsoft Access 2003 (bigint fields)
Submitted:	4 Aug 2005 19:48	Modified:	13 Sep 2007 17:56
Reporter:	Bogdan Degtyariov	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.51.11-2	OS:	Windows (Windows XP Pro SP2)
Assigned to:		CPU Architecture:	Any
Tags:	ODBC5-RC

Description:
When I connect from Microsoft Access 2003 and use Link Tables it shows all data within wvery column in the table as "#Deleted"
It appears that bigint does not translate into Access via MySQL ODBC 3.51.11-2-win.

How to repeat:
Run the following SQL:

 CREATE TABLE `TBL_MY_TEST` (
`CALL_ID` bigint(20) NOT NULL default '0',
`DOMAINID` varchar(20) NOT NULL default '',
`ORDER_SEQUENCE` tinyint(2) NOT NULL default '0',
PRIMARY KEY (`CALL_ID`,`ORDER_SEQUENCE`),
KEY `IDX_ORD_DETAIL_DOMAINID` (`DOMAINID`)
) TYPE=MyISAM

INSERT INTO TBL_MY_TEST VALUES (50802121204904219,'20050803101500',1);

Then try to browse the data from Access 2003 using ODBC connection

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.mysql.com/documentation/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

Additional info:

We suspect that the bug is on Access side. To demonstrate that suggestion we created a table with the same structure in Microsoft SQL Server 2000 SP4. Then we attempted to get the records from this table using MS SQL ODBC driver. Access displayed #Deleted values again.

See http://support.microsoft.com/kb/321901/en-us

Even MS says this doesn't work. Their suggested workaround:

"RESOLUTION
Use the data types Int or Text instead of the BigInt data type."

This is expected behaviour. Access doesn't know type "bigint".

See http://support.microsoft.com/kb/321901 and
http://dev.mysql.com/doc/refman/5.0/en/myodbc-usagenotes-apptips.html#myodbc-usagenotes-ap...

Solution would be to add support for SQL_C_NUMERIC (will be fixed later)

Because the solution to this is to support SQL_NUMERIC_STRUCT, this is a duplicate of Bug #3028.