Bug #4321 MyODBC 3.51.8(windows) return '????' when using Date format
Submitted: 29 Jun 2004 2:57 Modified: 29 Jun 2004 23:01
Reporter: Han Yoon Sup Email Updates:
Status: Can't repeat Impact on me:
Category:Connector / ODBC Severity:S1 (Critical)
Version: OS:Windows (windows 2000)
Assigned to: Dean Ellis CPU Architecture:Any

[29 Jun 2004 2:57] Han Yoon Sup
Server : Linux MySQL 4.0.20
ODBC : MyODBC 3.51.8(Windows)

I was Programming Visual Basic with ADO and MyODBC
until MyODBC Version 3.51.06 No Problem..
But I Got the Many Error in the My Program after 3.51.8 Version update

That Error happen because Date Format..
Using ADO and Get a Date Format Field...

ADO can't Get Any Data.. and Return '????'

How Can I Get the Right Date Format Data?...

No Problem in the 3.51.06 version...

How to repeat:
Ado Return '????' When get Date Field Data

Suggested fix:
i Want Right Date Format Data .. with MyODBC 3.51.8
[29 Jun 2004 23:01] Dean Ellis
I cannot repeat this; what MDAC are you using?  Can you submit a test case?
[30 Jun 2004 1:09] Han Yoon Sup
i am using MDAC 2.8 version...
[23 Aug 2005 11:25] Christopher Leeworthy
We had a repeat of this bug here.  Initially it seemed to only effect our windows XP machines not W2K or earlier.  But further examination showed the bug was dependent on which version of the ODBC driver we used.

Under MyODBC v3.51.06 dates returned as type 'variant/string' whilst v3.5.08 returned dates as type 'variant/bytearray'.  This was causing the application to crash on machines with the later MyODBC driver with an 'invalid type' message.

I can tell you that MyODBC v3.51.11 now returns dates as 'variant/string' which fixes the problem for us.

We develop for windows 95 through to XP using VB6.