Bob,
Thanks for the response. However, I am creating the Connection object in another COM object when the application starts up. The connection object is returned to the application and stored as a property of my application object. Whenever the application calls the COM object to perform a SQL command, it passes the connection object to the various COM methods (along with other parameters). The COM object then uses this connection object to create the Command and RecordSet objects which in turn, get returned to my application. Everything works fine when the client is running Windows 2000, the problem only exists on NT machines.

As a last resort, we can have the COM objects create the connection each time it is needed, however we didn't want have to constantly create and drop connections to SQL server.

Thanks,
Kurt