David78
07-11-2002, 02:02 PM
Hey gurus,
In an effort to help decide when to use client-side or server-side cursors in ADO, I have compiled the following chart. Feedback is welcome.
LEGEND
R = Required use
b = not required, but works better
use use
Client Server
------ ------
Local JET database R
Immediately view changes R
made by other users
Disconnected recordsets R
Asynchronous updates R
Shape commands R
(hierarchical recordsets)
Pessimistic locking R
Static updateable cursor R
(*see Note 1)
Records will be updated b
Large recordset; b
return FIRST record quickly
Large recordset; b
return LAST record quickly
Much back-and-forth scrolling b
Multi-row bound controls b
(i.e. grid, list box)
Batch Updates R
Note *1: If the cursor location is Server, and the cursor type is set to Static, and the Lock type is updateable, then ADO will change the cursor type to Keyset. (For a Client-side cursor and updateable Lock type, ADO will change the cursor type to Static.);)
In an effort to help decide when to use client-side or server-side cursors in ADO, I have compiled the following chart. Feedback is welcome.
LEGEND
R = Required use
b = not required, but works better
use use
Client Server
------ ------
Local JET database R
Immediately view changes R
made by other users
Disconnected recordsets R
Asynchronous updates R
Shape commands R
(hierarchical recordsets)
Pessimistic locking R
Static updateable cursor R
(*see Note 1)
Records will be updated b
Large recordset; b
return FIRST record quickly
Large recordset; b
return LAST record quickly
Much back-and-forth scrolling b
Multi-row bound controls b
(i.e. grid, list box)
Batch Updates R
Note *1: If the cursor location is Server, and the cursor type is set to Static, and the Lock type is updateable, then ADO will change the cursor type to Keyset. (For a Client-side cursor and updateable Lock type, ADO will change the cursor type to Static.);)