I have a VB Active dll project that works great. It opens up the 

connection to a SQL database using the ADO.Connection and manages all my 

database functions. I am making calls from APS and as long as I'm running 

the project from the VB environment the Connections to the Database are 

destroyed at the end of each ASP page. When I make it into a dll the 

connectivity remains as a process for several minutes.



It this normal or have I got something set wrong?



Thanks in advance - Judy

It sounds to me as if your watching the connection pool. When you close the

connection from COM the connection goes into a pool waiting for another

request for it...



Hal Levy

StarMedia Network, Inc.

Intranet Development Manager



-----Original Message-----

From: henryjud@n... [mailto:henryjud@n...]

Sent: Thursday, June 14, 2001 7:33 PM

To: ASP Database Setup

Subject: [asp_database_setup] VB ADO Connection remaining after closing

on SQL





I have a VB Active dll project that works great. It opens up the 

connection to a SQL database using the ADO.Connection and manages all my 

database functions. I am making calls from APS and as long as I'm running 

the project from the VB environment the Connections to the Database are 

destroyed at the end of each ASP page. When I make it into a dll the 

connectivity remains as a process for several minutes.



It this normal or have I got something set wrong?



Thanks in advance - Judy