>>>>>It may. But the ODBC has not been changed; something else changed. And then the ODBC stopped connecting to the SQL s
>>
>>Embolded: Speaking of driver file itself ? Or all settings ?
>>Why? AFAIR there is/was an option in connection strings as well to influence "defaults" to the setting used to establish the connection.
>>Probably "only" changes "access" keys in the registry, not any setting of/"inside" the SQL server installation, but I never looked in detail.
>>And changes made in the registry (which subkeys to load automagically) might influence your connection as well...
>>
>>>>Check your ODBC driver's documentataion (ha! you don't know where it is! - neither do I), there may be just another clause to add to the connectstring to make this work.
>>
>>One place to start might be connectionstring.com
>>
>>regards
>>thomas
>
>At this point I am not changing anything in the connection string, since tons of other desktops work fine. And I don't have access to the "offending" desktop so I would not be able to check anything. Not that I would even attempt to look at the registry. The IT is not screaming "bloody murder" which tells me that he either does not blame my app or find that this PC is not no 1 priority. I will let him "deal" with the guy who made the change, first. Then I will work with him on various changes.

Have you tried ODBC Data Source Administrator (e.g. run c:\windows\syswow64\odbcad323.exe) then check under Drivers for the driver you're using and check the version information? Perhaps the workstation that's having trouble has a different version of the driver ?