Scenario: Our install package used to add User DSN. We changed this to install System DSNs due to Terminal Servers and Citrix.
The problem is that some of these old User DSNs are floating around, and our application automatically chooses the User before the System and the connection info has changed as we upgraded server software.
I guess my question is, is there a way to force the application to use the System DSN over the User DSN if duplicates exist?
Our application is written in PowerBuilder 10.5 and we use SQL Anywhere 10.0.1.
Thanks, Calvin
The information about user DSN(s) are stored in the registry. Have you considered simply doing a couple registry reads and then either deleting/renaming the invalid DSN, or warning the user about the conflict and giving the user the option to repair the issue?