Re: Waiting for a recordset to finish fetching
- From: "Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom>
- Date: Thu, 26 Jul 2007 19:37:28 +0100
But, yeah, the point is that my theory is that ADO is still working on
building the recordset at the time the find executes.
How? Only if asynchronous.
If it Client-Sided and not asynchronous, it is never true.
Open() will not be returned from early.
Only when the last record is loaded will Open() return.
If it is Server-Sided, Find() does not work well AFAIK.
I am not even sure what it does.
Some day I will make some tests to find out.
Find() could, in theory, only work on the portion of the Recordset loaded in
memory.
Remember Server-Sided cursors are very very different from Client-sided.
For Server-Sided cursors, ADO is just a thin layer over what the database
provides.
Things like Filter, Sort, Find are designed to worked on client-sided
recordsets because all records are available in memory.
For server-sided recordsets you should use the SQL WHERE clause and ORDER BY
clause to do filtering, sorting, finding
My guess is you do have Server-sided cursor and are getting unpredicatable
results from Find().
Best bet is to change the CursorLocation to Client-sided.
Find() will work correct after that.
Stephen Howe
.
- Follow-Ups:
- Re: Waiting for a recordset to finish fetching
- From: William Vaughn
- Re: Waiting for a recordset to finish fetching
- References:
- Re: Waiting for a recordset to finish fetching
- From: Stephen Howe
- Re: Waiting for a recordset to finish fetching
- From: JoelB
- Re: Waiting for a recordset to finish fetching
- Prev by Date: Re: How to protect data within MS access?
- Next by Date: Re: Waiting for a recordset to finish fetching
- Previous by thread: Re: Waiting for a recordset to finish fetching
- Next by thread: Re: Waiting for a recordset to finish fetching
- Index(es):
Relevant Pages
|
|