CursorLocation Property (ADO)


		Contents Index Topic Contents

CursorLocation Property - ADO

Sets or returns the location of the cursor engine.
Applies To
Connection, Recordset
Settings And Return Values
Sets or returns a Long value that can be set to one of the following constants:

Constant Description

adUseClient Uses client-side cursors supplied by a local cursor library. Local cursor engines will often 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 some additional sensitivity to reflecting changes that others make to the actual 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 then become unavailable with this setting.

Remarks
This property allows you to choose between various cursor libraries accessible to the provider. Usually, you can choose between using a client-side cursor library or one that is located on the server.
This property setting only affects connections established after the property has been set. Changing the CursorLocation property has no effect on existing connections.
This property is read/write on a Connection or a closed Recordset, and read-only on an open Recordset.
Remote Data Service Usage When used on a client-side (ADOR) Recordset or Connection object, the CursorLocation property can only be set to adUseClient.
Examples
AbsolutePosition and CursorLocation Properties Example (VB)
See Also
Using OLE DB Providers with ADO

Top of Page
© 1997 Microsoft Corporation. All rights reserved. Terms of Use.

Constant	Description

adUseClient	Uses client-side cursors supplied by a local cursor library. Local cursor engines will often 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 some additional sensitivity to reflecting changes that others make to the actual 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 then become unavailable with this setting.