Bug #25432 TIME fields are not presented correctly
Submitted: 5 Jan 2007 13:38 Modified: 15 Jan 2007 9:15
Reporter: Tim Salter Email Updates:
Status: Duplicate Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:3.51.12 OS:Windows (Windows XP)
Assigned to: CPU Architecture:Any
Tags: access, ODBC, time

[5 Jan 2007 13:38] Tim Salter
Description:
The presentation of TIME field values via ODBC into MSOffice applications is incorrect.

How to repeat:
Create a single-row MySQL table with a TIME data field (and a primary key field, and a TIMESTAMP field populated with a non-null,non-zero value according to the Access ODBC workrounds to allow record updates)

Link to the table using MSAccess.

Open the linked table in Access, showing the single row.
Change the TIME field to 12:00
 - the TIME field value disappears from the Access representation of the field
Change the TIME field to 12:01:02
 - The TIME field value gets presented as the date 02/01/2012

Changing the preferred format of the field in the linked table to one of the time formats available makes problems worse.
 

Suggested fix:
Provide a (default?) ODBC driver option to make the retrieval of TIME fields compatible with MSOffice applications.
[9 Jan 2007 11:42] Tim Salter
This looks like another manifestation of bug 24867.
[15 Jan 2007 9:15] Tonci Grgin
Hi Tim and thanks for your problem report. This is indeed a duplicate of Bug#24867.
[1 Mar 2007 21:07] Bogdan Degtyariov
Duplicated by bug 25846