B
Boutang
I'm using Access 2003 as a reporting tool against a mySQL database,
connecting with the mySQL ODBC driver 3.51.17.
The ODBC driver reports every datetime field as a Long Integer in Access.
This makes date operations problematic.
I notice an interesting post in this forum from 2005 that would work fine
("Convert UNIX time to windows general date"), but using a function with
every row seems like an unnecessary performance hit. Also, it seems
counter-intuitive that the driver doesn't recognize the correct field type.
The problem looks suspiciously like the mySQL bug report #8363 (3.51.11
incorrectly describes Date field) shown at
http://bugs.mysql.com/bug.php?id=8363, but this bug is several years & many
versions old now -- I'm sure it would have been fixed.
Anybody experienced this before? Can you point me to a fix?
connecting with the mySQL ODBC driver 3.51.17.
The ODBC driver reports every datetime field as a Long Integer in Access.
This makes date operations problematic.
I notice an interesting post in this forum from 2005 that would work fine
("Convert UNIX time to windows general date"), but using a function with
every row seems like an unnecessary performance hit. Also, it seems
counter-intuitive that the driver doesn't recognize the correct field type.
The problem looks suspiciously like the mySQL bug report #8363 (3.51.11
incorrectly describes Date field) shown at
http://bugs.mysql.com/bug.php?id=8363, but this bug is several years & many
versions old now -- I'm sure it would have been fixed.
Anybody experienced this before? Can you point me to a fix?