MySQL Bugs: #76732: Will not connect properly to MS Access after first set up

Bug #76732	Will not connect properly to MS Access after first set up
Submitted:	17 Apr 2015 10:03	Modified:	21 May 2015 6:20
Reporter:	Matt Bowyer	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	Connector/ODBC 5.3.4 32 Bit	OS:	Windows (7)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
When connecting to MS Access using a file DSN, connector will work perfectly well the first time. However, if the file is saved and then re-opened, attempting to open any linked table will cause the login dialogue box to open with the username and password field blank - even writing the correct username and password in will not open the table, it will simply show the dialogue box with the username and password blank again.

Deleting and re-linking a single table, or using the 'linked tables manager', then clicking cancel on the login dialogue box (which then automatically brings up a browse box to look for the DSN file) will then allow all of the tables to be opened, until the next time the Access file is closed at which point one of the above steps will have to be repeated.

How to repeat:
Attempt to link a table in MS Access to an online MySQL database via ODBC and a file DSN, close the MS Access file (possibly need to restart the computer), re-open the MS Access file and attempt to open a linked table.

Hello Matt Bowyer,

Thank you for the bug report.
I tried to reproduce the issue at my end using Connector/ODBC 5.3.4 32 Bit, but not seeing any issues in username and password.
Also, to select 32-bit ODBC drivers you should run odbcad32.exe from WINDOWS\SYSWOW64\odbcad32.exe.
Could you please provide more information on this such as exact steps you tried, dummy application etc to repeat this issue at our end and/or screenshots to confirm the issue that you are facing? 

Thanks,
Chiranjeevi.

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