|
StevenWWinters
Starting Member
47 Posts |
 Posted - February 16 2005 : 20:01:15
|
The orders table in VPASP uses the TIME column type for the otime field.
There is a documented problem with the current versions (3.51.7 - 3.51.11) of myodbc driver which has the following symptoms.
1) myodbc returns a datetime field with the current date for the date portion instead of returning a time only value.
I have seen this on an a VPASP site hosted on Windows but using mysql as the database (VPASP's so-called UNIX version, running on Windows OS). In this case the code base is VPASP's Deluxe version which supports both mysql and SQL databases.
The bug is documented here:
http://bugs.mysql.com/bug.php?id=7046
http://bugs.mysql.com/bug.php?id=6336
http://bugs.mysql.com/bug.php?id=6026
You can see the effects of this (if the problem exists on your site) by viewing the otime field in the orders table using shopadmin.
2) Using Microsoft Access as a front end to view the VPASP tables (for querying and reporting), there is a problem with MS Access correctly interpreting the TIME field. Access will display what looks like a date field for what is really a TIME field. This may not be related to the myodbc driver but rather a problem with Access (I believe) not recognizing the TIME field as legitimate. I'm not really sure. To see it, connect to your mysql database using MSAccess through a myodbc connection and link to the orders table. Then view the table in Access.
The only place I've seen this documented is here:
http://www.issociate.de/board/post/162611/time_column_show_weird_date_values_in_MS_Access.html
If anyone else has seen either of these issues please respond to this post with any info you have.
Thanks!
|
|
All Forums
Mysql and Myodbc Problem With TIME Column Type
New Topic
Printer Friendly
Topic 
TrustGuard - PCI Security Scanner
