Bug #28546 | System DSN doesn't work at all with MSQry32 | ||
---|---|---|---|
Submitted: | 21 May 2007 6:13 | Modified: | 30 Nov 2007 7:40 |
Reporter: | Tonci Grgin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | 5.0.12-20071005 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | ODBC5-RC1 |
[21 May 2007 6:13]
Tonci Grgin
[29 Oct 2007 14:04]
Susanne Ebrecht
Hi Tonci, this is fixed in our new version of MyODBC. Please, try MyODBC 5.1. Thank you for trusting MySQL. Kind Regards, Susanne
[30 Nov 2007 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[30 Nov 2007 7:40]
Tonci Grgin
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at http://www.mysql.com/downloads/ Hi all and sorry for the delay. I confirm this is fixed both in 3.51 and 5.1 versions of driver: SELECT appointment0_0.GGUID, appointment0_0.Keyword FROM test.appointment0 appointment0_0 <<< ORDER BY appointment0_0.GGUID