Re: ADO results set vs. BDE
- From: "hajo" <hajospuunup@xxxxxxxxx>
- Date: 25 Apr 2008 07:25:46 -0700
"Bill Todd [TeamB]" <no@xxxxxx> wrote:
What is the problem you are trying to solve? In other words, why is
using a client side cursor and fetching the entire result set a problem?
It is difficult to suggest a solution without knowing exactly what
problem you are trying to solve.
--
Bill Todd (TeamB)
Well, the problem really is that our users are used to being able to perform a query that returns a large result set, but without having to wait around for all the results to be loaded. With the BDE, you could fetch a large results set a few records at a time. You wouldn't have to wait for all the results to be fetched first, which might take some time if there were a lot of results.
With ADO it seems that the entire result set must be fetched in one go, which could take a long time.
I know it would be preferable if we didn't fetch large result sets in the first place, but the BDE's behaviour was quite handy - e.g. if you accidentally did a wildcard search that pulled back a lot of results, you wouldn't have to wait. It would be great if this can be done in ADO too.
.
- Follow-Ups:
- Re: ADO results set vs. BDE
- From: Vitali Kalinin
- Re: ADO results set vs. BDE
- From: Bill Todd [TeamB]
- Re: ADO results set vs. BDE
- References:
- ADO results set vs. BDE
- From: hajo
- Re: ADO results set vs. BDE
- From: Vitali Kalinin
- Re: ADO results set vs. BDE
- From: hajo
- Re: ADO results set vs. BDE
- From: Bill Todd [TeamB]
- ADO results set vs. BDE
- Prev by Date: Re: ADO results set vs. BDE
- Next by Date: Strange AV deleting last record in access table
- Previous by thread: Re: ADO results set vs. BDE
- Next by thread: Re: ADO results set vs. BDE
- Index(es):
Relevant Pages
|