Re: CursorLocation -> Scrollbar behavior
- From: "Viatcheslav V. Vassiliev" <support@xxxxxxxxxxxxxxx>
- Date: Thu, 23 Mar 2006 22:21:51 +0300
For RecordNo OLEDB allows to return approximate value. Access may return
approximate value for RecordCount too. Both values are used by DBGrid. The
best solution for you is to use WHERE in command text and limit number of
rows returned for DBGrid.
//------------------------------------------
Regards,
Vassiliev V. V.
http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
ADO.Net
http://www.oledbdirect.com - The fastest way to access MS SQL Server,
MS Jet (Access) and Interbase (through OLEDB)
"LC" <lc@xxxxxxxxxxxx> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ:
news:44228e50$1@xxxxxxxxxxxxxxxxxxxxxxxxx
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:
- References:
- CursorLocation -> Scrollbar behavior
- From: LC
- CursorLocation -> Scrollbar behavior
- Prev by Date: TADOQuery and assign null value to the parameter
- Next by Date: Re: Connection String in SQL Server 2005 giving errors
- Previous by thread: CursorLocation -> Scrollbar behavior
- Next by thread: Re: CursorLocation -> Scrollbar behavior
- Index(es):
Relevant Pages
|
