I am using VB with ADO to connect to different databases in my SQLServer 2000.
1. First I open a database say, DB1, using ADO and it is not closed.
2. Second I open another database say, DB2, again using ADO & then close the ADO connection and set the connection object to nothing.
But then i notice in the enterprise manager that the SQLServer has a process still left open. And i need to detach the second database after i am done working on it. I actually take some data out of the first database and import it into the second database.
I cannot detach the second database, because the process created with the open connection operation still stays in the sqlserver processes.
But, If I close the open & close first connection before opening the second connection things are fine. But i need to keep the first connection open. So please help with information on why the second connection's process is still left open.
Thanks in advance,