RE: Omnis and Informix

we had a similar problem when we upgraded from client sdk 2.4 to 2.81, we are not using OMNIS but change the environment frequently, we found out that the setnet32 doesn't update the windows registry entries when switching the environment, so we are directly modifying the windows registry entries to set the environments (this is dangerous and not supported by informix) -----Original Message----- From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org]On Behalf Of a.bordes@anaafa.fr Sent: Wednesday, May 05, 2004 9:32 AM To: informix-list@iiug.org Subject: Omnis and Informix Hi, Has anyone seen this problem in any of your environments? The configuration is based on: IDS 7.31 FD (HP 11i 64 bit version) OMNIS using Informix Client SDK 2.80 We setup the setnet32 and set up a default configuration (dbservername, = protocol, ...). The OMNIS application connects to the default configuration of the = SETNET32. We want to change the default configuration without going out from the = application. The application written in OMNIS needs to switch IDS = instances. This worked fine using Client SDK 2.2 and IDS 7.30 (32 bits). = Now, it seems to only read the initial default SETNET32 configuration = and doesn't see the new modified one. Using setnet32 -l <saved config file> makes the changes to the registry, = by the application doesn't reread it again until you shut down the = application.=20 Has anyone seen this problem with the latest client SDK versions. Your help is appreciated. Thanks in advance. sending to informix-list