MySQL Bugs: #6845: SQLDriverConnect using connection string

Bug #6845	SQLDriverConnect using connection string
Submitted:	26 Nov 2004 12:04	Modified:	30 May 2013 12:14
Reporter:	Lincoln Ferreira	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	3.51.10	OS:	Windows (Windows 2000 Server)
Assigned to:		CPU Architecture:	Any

Description:
The SQLDriverConnect function using connection string on MyODBC driver version 3.51.10 don´t work on Windows 2000 Server environment.
Even using Microsoft ODBC Administrator to create a new DSN file using this driver.
On my application MyODBC return error code "6Y300 - [MySQL][ODBC 3.51 Driver] No DSN entered".
I tried these connection strings:
DRIVER={MySQL ODBC 3.51 Driver};SERVER=localhost;DATABASE=mysql;UID=test;PWD=test;OPTION=3;
DRIVER={MySQL ODBC 3.51 Driver};SERVER=localhost;DATABASE=mysql;USER=test;PASSWORD=test;OPTION=3;

Note: This method was working very well in MYODBC driver version 3.51.08.

How to repeat:
Lincoln Ferreira
lincoln@sincronica.com.br

Hi

I was unable to reproduce this problem with a small C++ test.  Can you please send us a test-case that reproduces this behaviour ?

Also, are you using MyODBC 3.51.10-2 ?

Thanks.

Hi,
I don´t have small test to send you, but the new pack 3.51.10-2 is ok for me.
The only problem is that SQLGetInfo(hdbc,SQL_DRIVER_VER,szVerDRV,15,NULL) return 3.51.10, so is impossible to verify the current version of MyODBC.
Regards,
Lincoln.

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".

Thank you for your bug report. This issue has already been fixed in the release version of that product, which you can download at

  http://www.mysql.com/downloads/