Re: Freeze in ADODB.Recordset.Open
From: Stephen Howe (stephenPOINThoweATtns-globalPOINTcom)
Date: 05/21/04
- Next message: Frank Petrucci: "Re: Timeout with Where statement"
- Previous message: Frank Petrucci: "Re: Timeout with Where statement"
- Maybe in reply to: Val Mazur: "Re: Freeze in ADODB.Recordset.Open"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 21 May 2004 14:35:34 +0100
> The problem is that, on some computers but not others, the call to .Open
> hangs -- it takes forever.
I don't have any answers Jonathan but I do have some suggestions (what I
would do was I there) :-)
1. On the computers that work and the others that fail, find out what
version of MDAC is on each and also Windows OS/Service Pack. It could be
that the ones that fail have a comon pattern. I would also check the state
of Connection caching in the registry. I would do this first, make a list of
the state of all machines and see if there is a common pattern to
success/fail.
2. Do you also start with
Dim mRS AS ADODB.Recordset
; recordset code in eample
and also
SET mRS = Nothing
when you have finished with the Recordset ?
3. For the machines where there is a successful Connect Open, I would do a
dump of the properties of the Connection Open (both before and after).
Frequently there are other dynamic properties that can be set that are
provider-specific.
Hope something here helps
Stephen Howe
- Next message: Frank Petrucci: "Re: Timeout with Where statement"
- Previous message: Frank Petrucci: "Re: Timeout with Where statement"
- Maybe in reply to: Val Mazur: "Re: Freeze in ADODB.Recordset.Open"
- Messages sorted by: [ date ] [ thread ]