Re: Waiting for a recordset to finish fetching

Stephen,

DoEvents did the trick. Sticking it in the middle of my loop instead of a
comment appears to have been exactly what I needed.

Thanks so much for your help!

Joel

"JoelB" wrote:

Stephen,

I guess I was being a little careless in my terminology regarding fetch.
But, yeah, the point is that my theory is that ADO is still working on
building the recordset at the time the find executes.

I'm a little rusty on DoEvents, but I'm thinking that your suggestion is
that sticking DoEvents in the loop would enable ADO to keep processing its
tasks, effectively breaking the 'log jam' that is currently occurring in my
loop...

I'll give it a shot.

Thanks,
Joel

"Stephen Howe" wrote:

First this "Waiting for a recordset to finish fetching" is only true if you
have opened the Recordset as asynchronous. If you have not, the Fetching
does not apply.
Asynchronous applies to client-sided curosrs

If you open a Recordset, client-sided and you have not specified
asynchronous, then the Open() call will not return until all records are
built up in client-sided memory.

If you open a Recordset, server-sided, then the Open() call will return as
soon as CacheSize records has been retrieved or the end of the records which
ever is first.

It is not specified what happens if you ask for Server-sided and
asynchronous.
I should imagine asynchronous is ignored.

Do While rs.State <> adStateOpen
' (nothing)
Loop

Surely you want

Do While rs.State <> adStateOpen
DoEvents
Loop

to give ADO more time to complete its action?

Stephen Howe







However, within the loop, the state never changes. I actually included a
timer to prevent an endless loop, and when I add a debug.print inside the
loop, even when I set it for 15 seconds it still stays in the fetching
state
(9) for the full period. I guess the fetch is stalled while loop is
running.

Can anyone suggest an alternate way to wait until the recordset is built
before doing the find?

The platform is MS Access.

TIA,
Joel




.

Relevant Pages

  • Re: DAO MUCH faster than ADO in this test
    ... DAO is well-known to be faster than ADO. ... Of course the DAO loop ran faster than the SQL loop; ... advantage of a table-type recordset, which only works on local tables. ... Dim starttime As Single, finishtime As Single ...
    (microsoft.public.access.modulesdaovba)
  • Re: Do While Loop nested in another While causes error
    ... still doesn't explain why a nested DO loop would cause problems. ... Until you sort out the contents of the recordset, ... idHolder = rsGuestbook ... display that new ID. ...
    (microsoft.public.inetserver.asp.db)
  • Re: One more ! Calculating Recordset Values
    ... Well I am almost there lol, got the recordset to work properly returning all ... the values in the one "loop" so to speak and I can see them being returned ... >> Dim aTot, eTot, iTot, pSubTot, aStrengthSubTot, PTotal, SubTotal, ... >>> totals ...
    (microsoft.public.frontpage.programming)
  • Re: One more ! Calculating Recordset Values
    ... EOF means that the end of the RecordSet has been reached. ... > 'Total = The sum of all the SubTotals ...
    (microsoft.public.frontpage.programming)
  • Re: Do While Loop nested in another While causes error
    ... still doesn't explain why a nested DO loop would cause problems. ... Until you sort out the contents of the recordset, ... display that new ID. ... response.Write the value of idHolder within the loopto see if it ...
    (microsoft.public.inetserver.asp.db)