Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sp_wiz
Yak Posting Veteran
55 Posts |
Posted - 2002-01-30 : 05:54:46
|
| Need some advice...I'm using a stored procedure that creates paged recordsets. The question i'm asking is what is the best Cursor type to use in ADO..Am i correct in thinking a Client side cursor would best suit, as the entire results are being used on the page each time. What pitfalls are there in using Client side cursors, someone mentioned that lower end machines ie win 95 with out the lates mdacs may not be able to deal with a client side cursor... Cheers Robp |
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2002-01-30 : 06:52:16
|
| Taken from VB6 help files:adUseClient Uses client-side cursors supplied by a local cursor library. Local cursor services often will allow many features that driver-supplied cursors may not, so using this setting may provide an advantage with respect to features that will be enabled. For backward compatibility, the synonym adUseClientBatch is also supported. adUseServer Default. Uses data-provider or driver-supplied cursors. These cursors are sometimes very flexible and allow for additional sensitivity to changes others make to the data source. However, some features of the Microsoft Client Cursor Provider (such as disassociated recordsets) cannot be simulated with server-side cursors and these features will be unavailable with this setting. |
 |
|
|
Nazim
A custom title
1408 Posts |
Posted - 2002-01-30 : 07:34:58
|
| if your requirement is paging , go thru the Articles, you will be able to pick some good points.http://www.sqlteam.com/SearchResults.asp?SearchTerms=Paging--------------------------------------------------------------Dont Tell God how big your Problem is , Tell the Problem how Big your God isEdited by - Nazim on 01/30/2002 07:36:23 |
 |
|
|
|
|
|