MySQL Bugs: #24874: MyODBC error (-7776) in Access using a linked table with MySQL TIME data type

Bug #24874	MyODBC error (-7776) in Access using a linked table with MySQL TIME data type
Submitted:	7 Dec 2006 5:42	Modified:	24 May 2007 20:33
Reporter:	Erica Moss	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	5.00.09	OS:	Windows (win XP sp 2/Access 2003)
Assigned to:	Erica Moss	CPU Architecture:	Any

Description:
Received this error when opening a table with two columns, (int, Time).  The table has just one record (1, current_time())

"Reserved error (-7776); there is no message for this error"

The table fails to open in Access and the error is received a few times and then again every 10 seconds or so.  The attached trace file is quite long but this is just from a single attempt to open the table with only one record.  It appears to go through the same sequence a number of times, but there is no apparent error in it.

I also attepted this with a third column of Timestamp but the behavior was identical.

How to repeat:
CREATE TABLE timetable (c1 INT AUTO_INCREMENT PRIMARY KEY,c2 TIME);
INSERT INTO timetable (c2) VALUES (CURRENT_TIME());
SELECT * FROM timetable;
+----+----------+
| c1 | c2       |
+----+----------+
|  1 | 23:36:28 |
+----+----------+

Link this table in Access, and attempt to open the table. 
Errors are received.

trace file

Attachment: SQL.LOG (application/octet-stream, text), 88.32 KiB.

verifying fix

Verified Fix using 5-24-07 build.  It is necessary to apply a mask to the Access table or form to prevent the display of a Date since Access only has a Date/Time data type.