Bug #10000 MyODBC newer than 3.51.06 doesn't send time correctly to Crystal Reports 8.5
Submitted: 19 Apr 2005 15:33 Modified: 19 Apr 2005 18:16
Reporter: Alasdair Barclay Email Updates:
Status: Duplicate Impact on me:
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51.11-2 OS:Microsoft Windows (Windows XP Pro)
Assigned to: CPU Architecture:Any

[19 Apr 2005 15:33] Alasdair Barclay
I'm using Crystal Reports Developer v8.5 to display data held in a MySQL Database (v4.1.9), using MyODBC.  Some of the fields are Time fields, and using MyODBC 3.51.06 these displayed correctly.  However, when I upgraded to MyODBC 3.51.9, the times were displayed as 00:00:00.  This also happens with versions 3.51.11-1 and 3.51.11-2.  When I revert to version 3.51.06 (remembering to manually delete myodbc3.dll, myodbc3.lib and myodbc3d.dll from the system32 directory) the times are displayed correctly.

How to repeat:
Upgrade from MyODBC 3.51.06 to 3.51.9 or later.
[19 Apr 2005 17:57] Heikki Tuuri

Bug report #10 000 is a major milestone!

Best regards,

[19 Apr 2005 18:16] MySQL Verification Team
Same related issue (handling [date]time fields) as:


Thank you for the bug report.
[25 Apr 2005 7:26] Alasdair Barclay

May I point out that the bug I am seeing happens on every time field, not the last TimeStamp field as with bug #9927.

Alasdair Barclay