CursorLocation -> Scrollbar behavior

From: "LC" <lc@xxxxxxxxxxxx>
Date: Thu, 23 Mar 2006 13:02:15 +0100

Hi,

Im using XP -> D7 -> ADO -> MSAccess.

The data in some of my customers DBs have grown, making DBGrids very slow.
Wherefore I have changed the TADODataset.CursorLocation to clUseServer, and
now the data is presented a lot faster.

However, the scrollbar now works in like 3 steps, making it almost
impossible to use.
I guess this has to do with the fact, that the ADO cursor have no clue where
its located in the table, when the Cursorlocation is set to Server.

Does anybody no how to fix this?
Is there a way to set the CursorLocation to clUseServer for performance, and
still have a 'working' scrollbar in the DBGrid?

Thanks a lot
LC

.

Follow-Ups:
- Re: CursorLocation -> Scrollbar behavior
  - From: Viatcheslav V. Vassiliev

Prev by Date: Re: Access violation error on domain only
Next by Date: Re: Problems with numeric columns in Oracle
Previous by thread: Access violation error on domain only
Next by thread: Re: CursorLocation -> Scrollbar behavior
Index(es):
- Date
- Thread

Relevant Pages

CursorLocation = clUseServer Problem
... two session of the application at the same time. ... it seems that the second time the application wait until ... I want to set the CursorLocation to clUseServer in order to prevent a user ...
(borland.public.delphi.database.ado)
Re: ADO performance
... I move CursorLocation = clUseServer before CursorType = ctOpenForwardOnly ... I will continue searching ... Guillermo ...
(borland.public.delphi.database.ado)
Using TADODataset with DB2
... I am using a TADODataset component with CursorLocation = clUseServer and CursorType = ctDynamic. ... 'Multiple-step OLE DB operation generated errors. ...
(borland.public.delphi.database.ado)