Multiple ODBC connection problem with INET7

Hello, We are having a problem after establishing multiple ODBC connections. We have this problem when we are using 32-bit Inet 7 along with Intersolv's Informix 7 ODBC driver in NT. We do not get this problem with 32-bit Inet 5 and Intersolv's Informix 5 driver. The problem is best explained by an example: First, run two copies of Microsoft Query (16-bit) and establish two connections to the same database. You can switch between the two and see that they are both active. You can also go to the server and see that you have established two separate connections. When you close one copy of Query, the other one loses the connection. I can also duplicate this with a number of other 16-bit ODBC applications. This does not seem to be a problem when running 32-bit applications. Also, if I set up the icon for Query/16 so that each copy runs in its own memory space, it works fine. It only seems to happen with two 16-bit applications which run in the same memory space. Our specific problem is that we have written a VB 3.0 application which uses Crystal Reports to display some reports. The problem is that since Crystal Reports establishes a second connection, after the user views a report, our application has lost its connection to the database. I would switch back to Inet 5 but we've encountered different problems with that too. Besides, I'd like to stay with the most current release. Here are the versions we are using: 32-bit Inet7 version 7.10.TC1 (ISQL710.DLL 5/21/95 460,288) 32-BIT Intersolv Informix 7 ODBC driver v2.12 (IVINF709.DLL 2/8/96 113,744) We have duplicated this problem on different client workstations and against different back-end databases. At our site we have an Online Workgroup Server for NT version 7.12.TC3. At another site we've duplicated the problem against an Online Dynamic Server for AIX version 7.1. I have spoken with Intersolv tech support but they just gave me a blanket statement that they don't support running 16-bit software with their 32-bit ODBC drivers. However, they also say that you can't use a 16-bit ODBC driver in a 32-bit environment. So, they are basically saying that they don't support any 16-bit applications in Windows NT or 95. Nice. Has anyone else encountered this problem? If so, is there something I can do to fix it? Thanks for your help. Jay Sullivan.