Re: TADOConnection.Close does not work
- From: "Steve Bailey" <sbailey@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 23 Apr 2007 11:56:28 +0100
I have just checked and can confirm that Connection Pooling is actually
disabled on my development machine so, unfortunately, it looks like it is
not the cause of my problem.
"Steve Bailey" <sbailey@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:462c906d@xxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for that, Vitali.
Is there any way I can switch off Connection Pooling (at least
temporarily) from within my application?
"Vitali Kalinin" <vitkalinin@xxxxxxxxx> wrote in message
news:462c6c55$1@xxxxxxxxxxxxxxxxxxxxxxxxx
Most probably you are observing ODBC connection pooling in action. -
"When the application releases the connection, the pool returns S_OK to
the user, simulating a successful disconnection from the database.
However, the actual connection is not released by ODBC but instead waits
in the pool. When the next request for a connection to the database that
has the same data source and user information comes in, it is satisfied
from the connection in the pool rather than by making a full connection
to the database."
.
- Follow-Ups:
- Re: TADOConnection.Close does not work
- From: Vitali Kalinin
- Re: TADOConnection.Close does not work
- References:
- TADOConnection.Close does not work
- From: Steve Bailey
- Re: TADOConnection.Close does not work
- From: Vitali Kalinin
- Re: TADOConnection.Close does not work
- From: Steve Bailey
- TADOConnection.Close does not work
- Prev by Date: Re: TADOConnection.Close does not work
- Next by Date: Re: Parameter value as null
- Previous by thread: Re: TADOConnection.Close does not work
- Next by thread: Re: TADOConnection.Close does not work
- Index(es):
Relevant Pages
|
|