Sets or returns the location of the cursor engine.
Settings And Return Values
Sets or returns a Long value that can be set to one of the following constants.
| Constant | Description |
| adUseNone | No cursor services are used. (This constant is obsolete and appears solely for the sake of backward compatibility.) |
| adUseClient | Uses client-side cursors supplied by a local cursor library. Local cursor engines 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. |
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 affects connections established only 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.
Connection.Execute cursors will inherit this setting. Recordsets will automatically inherit this setting from their associated connections.
Remote Data Service Usage When used on a client-side (ADOR) Recordset or Connection object, the CursorLocation property can only be set to adUseClient.