Re: CursorLocation -> Scrollbar behavior

OLEDB specification allows driver to return approximate RecordCount and
RecordNo if return exact number is expensive (takes much time, resources).
For client-side cursor when all data are cached return exact
RecordCount/RecordNo is not a problem.

//------------------------------------------
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:4426ad66@xxxxxxxxxxxxxxxxxxxxxxxxx

Thanks for replying,

What do you mean exactly?
Is the reason for the increase of speed, when using Server based cursors,
that the RecordNo is'nt exact. (RecordCount works ok)
Do you think the problem is in the driver, or is it the Access DB thats
simply not able to provide info.

Is this a common problem, or does is work with the SQL Server?

I would imagine that this is something other customers have experienced as
well.
Im already limiting a lot with WHERE clauses in the commandtext property.

Thanks
LC


"Viatcheslav V. Vassiliev" <support@xxxxxxxxxxxxxxx> wrote in message
news:4422f550$1@xxxxxxxxxxxxxxxxxxxxxxxxx

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











.

Relevant Pages

  • Re: Any Recordset stays empty when using SQL Native Client
    ... Even the UDL Dialogue produces parameter names with spaces, ... Additionally I eliminated the "As New" declares. ... The problem is expecting the RecordCount to always 'work'. ... You need to use a client-side cursor, or a server-side with static, keyset, ...
    (microsoft.public.vb.database.ado)
  • Re: Help with IIS server Error (Provider error 80040154 Class not registered)
    ... Mr. Barrows ... page on my ISP's web server. ... > determines whether or not the cursor supports recordcount. ...
    (microsoft.public.inetserver.asp.general)
  • Re: Please help with cmd.execute select SQL?
    ... > What is the proper format for my SQL str using command.execute? ... RecordCount requires the use of an expensive cursor. ... and connection immediately, releasing the connection back to the connection ...
    (microsoft.public.inetserver.asp.general)
  • Re: ADO Record Count Issue
    ... Your dynamic cursor allows for runtime updates so it can not determine the ... RecordCount a lot and all of those queries use adOpenStatic for the cursor ... and then the the information is pushed on to an Excel ...
    (microsoft.public.vsnet.debugging)
  • Re: recordcount = -1 ??
    ... You don't need to use Recordcount, ... cursor, ... Looping through an array is much more efficient than looping through a ... Please reply to the newsgroup. ...
    (microsoft.public.inetserver.asp.db)