For a long time I had a problem with Windows XP Pro systems that had NI-DAQ installed. These machines were ATE controllers which had Labview applications deployed with NI-DAQ cards. I needed database connectivity through several system DSN's for Access, Pervasive, and SQL server. The problem was that after I installed NI-DAQ all the system DSN's would disappear in the Data Sources control panel in windows. Then if I tried to create them again it would say they were already there. I could actually edit them by name, delete them and recreate them, but they would not appear in the WinXP Data Sources Manager. They would exist, but would be invisible. They actually worked fine from an application perspective, but would be a pain to edit or know if I had set one up or not.
I finally solved it with the help of my network admin and I wanted to post the solution for someone else with the same problem:
I solved the invisible ODBC problem. NI installs an ODBC DSN called Citadel 4. When this is installed it adds its entry via a registry setting. The problem is it changes the "Default" key in HKLM\Software\ODBC\ODBC.INI from "No Value Set" to blank. For some reason, when ODBC Manager reads the list in this key, the blank screws it up. Deleting the Default setting causes the Default setting to be recreated as No Value Set and all appears again.
-Devin
I got 99 problems but 8.6 ain't one.
