Re: TADOConnection.Close does not work
- From: Brian Bushay TeamB <BBushay@xxxxxxxxx>
- Date: Tue, 24 Apr 2007 21:46:50 -0500
OK. BTW, my original post asked about TCustomConnection.DoDisconnect beingI don't know of one.
empty. I should, of course, have looked further than that. DoDisconnect is
a virtual method, overridden by TADOConnection.DoDisconnect, which calls
TADOConnection.ConnectionObject.Close. After that it calls code which, I'm
afraid, is beyond me.
My TADOConnection's Provider is "Microsoft OLE DB Provider for ODBC Drivers
(MSDASQL.1)". One of the first ODBC calls MSDASQL must make is to
initialize the ODBC environment: "SQLAllocHandle". This returns a handle.
Is there any way of getting at this handle through TADOConnection? (If
there is then I can call SQLDisconnect myself.)
Why do you want to use ODBC for SQL Server when there is a more capable OLE Db
provider for SQL server?
--
Brian Bushay (TeamB)
Bbushay@xxxxxxxxx
.
- Follow-Ups:
- Re: TADOConnection.Close does not work
- From: Steve Bailey
- Re: TADOConnection.Close does not work
- References:
- TADOConnection.Close does not work
- From: Steve Bailey
- Re: TADOConnection.Close does not work
- From: Brian Bushay TeamB
- Re: TADOConnection.Close does not work
- From: Steve Bailey
- TADOConnection.Close does not work
- Prev by Date: Re: Time Delay in opening a Table
- Next by Date: Re: TConnection.Open question
- Previous by thread: Re: TADOConnection.Close does not work
- Next by thread: Re: TADOConnection.Close does not work
- Index(es):
Relevant Pages
|