Visual Basic: RDO Data Control
rdoDefaultCursorDriver Property
See Also Example Applies To
Returns or sets the cursor library used by the ODBC driver manager.
Syntax
object**.rdoDefaultCursorDriver** [= value]
The rdoDefaultCursorDriver property syntax has these parts:
| Part | Description |
| object | An object expression that evaluates to an object in the Applies To list. |
| value | An Integer constant or value that specifies a type of ODBCcursor as described in Settings. |
Settings
The settings for value are:
| Constant | Value | Description |
| rdUseIfNeeded | 0 | (Default)RDO chooses the style of cursors most appropriate for the driver. Server-side cursors are used if they are available. |
| rdUseODBC | 1 | RDO uses the ODBC cursor library. This option gives better performance for small result sets, but degrades quickly for larger result sets. |
| rdUseServer | 2 | RDO uses server-side cursors. For most large operations this gives better performance, but might cause more network traffic. |
| rdUseClientBatch | 3 | RDO uses the optimistic batch cursor library as required by all batch mode operations and dissociate rdoResultset objects. |
| rdUseNone | 4 | RDO does not create a scrollable cursor. Basically, this is a forward-only, read-only resultset with a RowsetSize set to 1. This type of resultset performs faster than those that require creation of a cursor. |
Remarks
When server-side cursors are used, the database engine uses its own resources to store keyset values. Data values are still transmitted over the network as with client-side cursors, but the impact on local workstation memory and disk space is reduced.
For SQL Server, server-side cursors are not used if the cursor is read-only and forward-only.