Re: ADO results set vs. BDE
- From: "hajo" <hajospuunup@xxxxxxxxx>
- Date: 25 Apr 2008 06:25:34 -0700
"Vitali Kalinin" <vitkalinin@xxxxxxxxx> wrote:
"hajo" <hajospuunup@xxxxxxxxx> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ:
news:4811bb9c$1@xxxxxxxxxxxxxxxxxxxxxxxxx
Can TADOQuery be made to behave like the BDE TQuery component and onlyYou can achieve something like that with ServerSide cursors, for details see
fetch a few records at a time, or can it only fetch all the results?
TADODataSet.CursorLocation. Also it is not recommended to use them in GUI
due to performance considerations and numerous behavior restrictions.
Thanks Vitali. Part of our application uses a TDBGrid to display search results. You say that Server side cursors are not recommended for GUI use - for the TDBGrid, should we just accept that we have to use a client side cursor and fetch all results, or is there anything else we could do?
.
- Follow-Ups:
- 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
- ADO results set vs. BDE
- Prev by Date: Re: ADO results set vs. BDE
- Next by Date: Re: ADO results set vs. BDE
- Previous by thread: Re: ADO results set vs. BDE
- Next by thread: Re: ADO results set vs. BDE
- Index(es):