Slow Response Time using ODBC to access an Informix database

We are installing a vendor-supplied application, which uses an ODBC connection to access data in an Informix database. On some workstations response time is quite good, but on similar ones, it takes minutes to go from one screen to another. We are stumped as to why? We are running IDS 7.30.UC3X3 on a 4-CPU AIX RS6000 F50 server. The server workload was extremely light when we were testing this application. The application is MakroMed's InfoMed which uses Paradox version 7 for the GUI. We are installing it on Windows NT 4.0 workstations. To troubleshot this problem, we started from the ground up on two typical workstations. Both are HP Vectra Model VL5/166 with 64MB of memory. On each machine, we took the following steps: * Window NT 4.0 with Service Pack 3 was loaded from our standard image.. This standard image contains Windows NT and standard applications like Microsoft Office 97. * Network drivers and IP addresses were established. * Informix IConnect 2.01 software containing the Intersolv DataDirect 3.01 Driver was loaded. * Informix SETNET32 settings were established. * A user ODBC data source was defined. * Paradox version 7 was loaded. * The InfoMed application was loaded and the ODBC connection was defined. * The InfoMed application was launched. On the first workstation response time was good. On the second workstation it was not. Further investigation disclosed that workstation #2 had a newer network card and driver. We removed the network card from workstation #2 and installed it into workstation #1. After rebooting, response for the application was still good. So we removed the 3COM Fast EtherLink XL PCI 10/100 Mb Adapter (3C905) driver from workstation #1 and added the 3COM Fast EtherLink XL PCI 10/100 Mb Adapter (3C905-TX) driver, which was being used by workstation #2. Upon reboot, workstation #1 acted like workstation #2. It took minute(s) to go from screen to screen. We went back to the Control Panel -> Network panel, removed this network driver, and re-added the old one. Performance remained poor. Can anyone suggest a likely root cause of this problem? Or provide us with tips on how to troubleshoot those problem? We no longer believe that it is caused by Informix or MakroMed client software, because we were able to recreate the problem without touching either set of software. Unfortunately we are still unable to remedy the problem once it occurs on a workstation. On workstations with poor InfoMed response time, slower response time can also be observed with another application that uses MS Access97 for the client interface. Your assistance in resolving this strange problem would be greatly appreciated. Rick Bernstein Rick Bernstein Principal Database Administrator Alaris Medical Systems rbernste@alarismed.com