Re: ADO - Bad when it is time to Optimize
- From: "Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom>
- Date: Sun, 11 Mar 2007 21:05:23 -0000
I don't see this discussed a lot, so let me add this:
The SQLOLEDB povider has a dynamic property that will prevent this
connection creep by raising an error rather than creating a second
connection.
That is interesting.
I ought to go over the dynamic properties for each object some time.
Thanks Bob.
.
- References:
- ADO - Bad when it is time to Optimize
- From: cvsudheer
- Re: ADO - Bad when it is time to Optimize
- From: Bob Barrows [MVP]
- Re: ADO - Bad when it is time to Optimize
- From: cvsudheer
- Re: ADO - Bad when it is time to Optimize
- From: Stephen Howe
- Re: ADO - Bad when it is time to Optimize
- From: Ralph
- Re: ADO - Bad when it is time to Optimize
- From: cvsudheer
- Re: ADO - Bad when it is time to Optimize
- From: Bob Barrows [MVP]
- ADO - Bad when it is time to Optimize
- Prev by Date: Re: ADO - Bad when it is time to Optimize
- Next by Date: CCommand Open freezing.
- Previous by thread: Re: ADO - Bad when it is time to Optimize
- Next by thread: Re: Public member not found
- Index(es):