Bug #8384 DateTime Fields Interpreted by Access as Text
Submitted: 9 Feb 2005 4:46 Modified: 9 Feb 2005 5:53
Reporter: Geoffrey Poole Email Updates:
Status: Duplicate Impact on me:
Category:Connector / ODBC Severity:S1 (Critical)
Version:3.51.11 OS:Microsoft Windows (Win2K)
Assigned to: CPU Architecture:Any

[9 Feb 2005 4:46] Geoffrey Poole
I just upgraded my ODBC Connector to 3.51.11 and have encountered the following problem that has stopped the use of my database dead in it's tracks...

When linking a MySQL table (via File->Get External Data) into MS Access, all DateTime and TimeStamp fields in the MySQL database are interpreted by Access as Text fields.  With previous drivers, Access had interpreted these fields at "Data/Time" fields.

Table type is MyISAM

MySQL server verion 3.23.56

How to repeat:
In MS Access 2002, use File->Get External Data->Link Tables menu command to link a table that has a "DateTime" type field.  In database window, select linked table and click "Design."  Access will display field type as Text.

Suggested fix:
Reinstate old behavior where Access can recognize "DateTime" field type and considers the field to be "Date/Time" within Access.

Work around might be to use the "CDate()" function in MS Access, but in my case, that would mean hunting through thousands of lines of code and making hundreds of changes...

Also, I have no idea if the TimeStamp fields work correctly.  I haven't dared to make any updates to the database for fear of corrupting data files...
[26 Apr 2005 20:56] [ name withheld ]
This also occurs with InnoDB tables, 4.0.13-standard, and access 2002 sp3.  I am also stopped dead after upgrade to win XP and installing 3.51.11. Also was unable to fall back on the old version (3.51.10) without getting fatal errors.  Is there a proper way to drop back or is this version not going to work with win XP?  Any progress on the bug?
thanks very much