Re: EOAsyncFetchNonBlocking Question
- From: "Randy Adanza" <radanza@xxxxxxxxxxx>
- Date: Fri, 16 May 2008 09:28:30 +0800
Paul,
This is the solution I've found while googling, it seems to be a known bug.
Just place this code inside the OnAfterScroll event of TADOQuery.
if DataSet.Bof or DataSet.Eof then
begin
DataSet.DisableControls ;
with TCustomADODataSet ( DataSet ) do
begin
if Bof then
Recordset.MoveFirst
else
if Eof then
Recordset.MoveLast ;
CursorPosChanged ;
Resync ( [ ] ) ;
end ;
DataSet.EnableControls ;
end ;
Randy.
"Paul Scott" <paul.scott@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:op.ua6zq0mjjpqj2l@xxxxxxxxxxxxxxxxxxxxxxxx
Randy,
On Thu, 15 May 2008 08:39:27 +0100, Randy Adanza <radanza@xxxxxxxxxxx>
wrote:
Then I found out that by setting TADOQuery.ExecuteOption to
EOAsyncFetchNonBlocking speeds up things quite nicely. However, I found
out that it seems to bypass the First and
Last record, I did however found a fix for that.
Would you care to share your solution?
--
Paul Scott
Information Management Systems
Macclesfield, UK.
.
- Follow-Ups:
- Re: EOAsyncFetchNonBlocking Question
- From: Paul Scott
- Re: EOAsyncFetchNonBlocking Question
- References:
- EOAsyncFetchNonBlocking Question
- From: Randy Adanza
- Re: EOAsyncFetchNonBlocking Question
- From: Paul Scott
- EOAsyncFetchNonBlocking Question
- Prev by Date: Re: Return value in stored procedure
- Next by Date: Re: EOAsyncFetchNonBlocking Question
- Previous by thread: Re: EOAsyncFetchNonBlocking Question
- Next by thread: Re: EOAsyncFetchNonBlocking Question
- Index(es):
Relevant Pages
|
|
