MySQL Bugs: #118883: The ODBC connector definition GUI does not present or use existing values when editing sources

Bug #118883	The ODBC connector definition GUI does not present or use existing values when editing sources
Submitted:	22 Aug 10:31	Modified:	27 Aug 15:04
Reporter:	Horst Wieland	Email Updates:
Status:	Analyzing	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	8.4x, 9	OS:	Windows (10, 11)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	GUI

Description:
Starting with V.8, in some environments the ODBC Connector GUI to define a data source always appears to forget it's parameters for System DSNs, despite these are written into HKLM\Software\ODBC correctly.

The server name and the password are written into the data source key after having defined them.
The data source works fine then!

With certain installations re-editing the data source by ODBCAD32 does not present some values with the GUI, which had been defined previously, despite the key still holds these. Namely a subset of User name, password and even the sever name.
When trying to test the connection by the GUI right after opening the data source it fails, unless server name and password and sometimes user name got re-entered inside the GUI.

This only happens with certain environments.
What might be wrong with these?

I recently also was confused, the data source cannot be configured to "enable auto reconnect" or use a distinct charset any more. That was clearly announced in release informations though.

Nevertheless it's still confusing, the GUI still offers those options even with the newest connectors, but does not use them any more and removes those registry values accordingy when saving.

How to repeat:
Unknown. It does not happen with my own system. I noticed this frequently with several other systems, which stubbornly refuse to work identical then.

Suggested fix:
Fix the ODBC GUI to respect connector-version specific options and always present existing values from the registry key(s), if applicable.

Hi,

I am having issues reproducing this. Can you try to upgrade to latest connector i the env. where you can reproduce the problem? Does it solve it?

As mentioned I also have issues reproducing the disappearing entries of password, server and sometimes user name with my system. It's O.K there and it ever was with all connectors. Current and previous ones.

Only the options, which don't work any more are present inside the GUI still. 
Unfortunately I didn't note where this happened recently. There are some environments. It would be interesting which system details might be needed to find in order find a reason why this happens there. Legacy libraries?
It happend with new Windows 11 systems as well as with Windows 10 before and also wit 8.0.x drivers as I remember.

additional comment. 

A colleague of mine yesterday used the newest connector 9.4, where this also happened. 

Anything to look for in such environments? I now know a case where to check.

I'm discussing this with connector team. So far we have no solution.

today i checked a system where this happened yesterday. Today the values didn't disappear when editing the data source.

Might this happen right after installing or updating the connector anew before a reboot occured? (The customer proposed this)

Nevertheless, the additional Options in "Details" which are depreciated are present still and are misleading.