MySQL Bugs: #16640: Access crashes while linking table and providing PW and DB name at connect time

Bug #16640	Access crashes while linking table and providing PW and DB name at connect time
Submitted:	19 Jan 2006 17:09	Modified:	25 Jul 2007 22:57
Reporter:	Elim Qiu	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	3.51.12	OS:	Windows (win2k)
Assigned to:		CPU Architecture:	Any

Description:
This may not seen to others but i used eomodeler to connect mysql server via odbc. There is a connection penal where i put the connection info such as host, database and user etc. Click the submit button will cause error msg saying that the connection is cancelled by user!

It's critical to me but may not to others. Anyway 3.51.11 worked perfectly to me.

How to repeat:
If WebObjects 4.5.1 is installed on win2k, just try to connect mysql db from eomodeler

Suggested fix:
I think that may related to the odbc api standard. If the changes from 3.51.11 is based on NEW standard, nothing should be fixed. And I can just live with 3.51.11

MySQL Connector/ODBC 3.51.12 Doesn't have any changes in ODBC API standard. Since the version 3.51.11 there were added some bugfixes and improved the compatibility with MySQL Server 5.0

Error inside Access

Attachment: bug16640.PNG (image/x-png, text), 31.70 KiB.

I was able to repeat (picture attached) when creating the DSN with
the Windows ODBC manager without to fill the user and its password
then when prompted inside Access and filling the user and password
text boxes and pressing the OK button, that message is displayed.

If it were possible to download the old connector (3.51.11) it would solve the problem for a lot of us.  Could you let us know where it is available?

I received this using msquery and excel.  I fixed it by going to [Advanced] tab in odbc settings, clicking on the [Flags 2] sub tab, then making sure "Don't Prompt Upon Connect" was checked.

I'm not sure what version of the driver Miguel used to reproduce this.  I tried it with 3.51.17 on Access, and when I get to the end of these steps, Access crashes:  

Created a user DSN with values, DSNname, server-localhost, UID-root, PW,and DB fields were null
Created a new DB in Access, and selected File/Get Ext Data / Link tables
Selected ODBC from the type drop down, and chose the new DSN from the list of machine sources.
The MyODBC config app loaded and I entered the PW, and manually typed in the name of the MySQL database
(It was necessary to remove the errant space which was already present in that field)

After selecting OK, Access 2003 crashed.  I repeated this a number of times.  Due to the crash I'm raising the sev and priority level.

This is already fixed for 3.51.18. (I can reproduce with 3.51.17, but not with a driver compiled from the latest SVN trunk.)

Well, on my XP box it is *not* repeatable with 3.51.17... Using old DSN, removed username and password (as a matter of fact, before I didn't have password set at all, just changed it on a server) and tried to import data to Access. Everything works on database with ~100 tables with ~20 crashed ones... AFAIS this must have something to do with options used.

Will retest with .18 to determine which if any options are required to support this feature