Orphaned DSNs after deinstalling I-Connect

Dear Informixers, I had already asked this question in another context, but since there were no answers, I'm trying again with another subject. I came across a number of machines where a previous version of I-Connect had been deinstalled and the newest I-Connect 2.90TC4 installed. Now there are some DSNs pointing to Informix databases that cannot even be removed because the old version is missing and no new DSN of the same name can be configured because the old one is still sitting around. And there are applications that need that DSN name... The only way to deal with Informix DSNs in an upgrade situation seems to be to delete the DSN before deleting the old version of I-Connect and then recreating the DSN after installation of the new version. Or is there a method of migrating the DSN to the new version? I had hoped that "DSN Migrate" might do this, but apparently it doesn't. Regards, Richard

Richard Spitz wrote: > The only way to deal with Informix DSNs in an upgrade situation seems to > be to delete the DSN before deleting the old version of I-Connect and > then recreating the DSN after installation of the new version. Or is there > a method of migrating the DSN to the new version? I had hoped that "DSN > Migrate" might do this, but apparently it doesn't. I don't know about migration. This probably isn't the answer you're looking for but you can delete DSN entries through the Windows registry if you can't remove them through the ODBC interface. The key is HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBC.INI I don't think doing this has any ill effects but as with all registry hacks be careful and consider backing up what you delete first. Ben.