%META:TOPICPARENT{name="InstallConfigOLEDB"}%
= Controlling ODBC Cursor Library Usage with the Single-Tier "Lite" Edition OLE DB Provider for ODBC Data Sources =

The Single-Tier "Lite" Edition OLE DB Provider for ODBC Data Sources requires that the target ODBC driver support some form of scrollable cursor for any connection. To fully support OLE DB rowsets, the minimum requirements are --

* bookmark support
* absolute cursor positioning
* backward scrolling

<code>KEYSET DRIVEN</code> and <code>STATIC</code> cursors both support this functionality. 

If the Single-Tier "Lite" Edition OLE DB Provider for ODBC Data Sources is to be used with an ODBC driver which natively supports neither <code>KEYSET DRIVEN</code> nor <code>STATIC</code> cursors, then the Microsoft ODBC Cursor Library must be used. The Microsoft ODBC Cursor Library only supports <code>STATIC</code> cursors, but this is generally sufficient. 

All <nop>OpenLink ODBC drivers support both <code>KEYSET DRIVEN</code> and <code>STATIC</code> cursors, and it is best to use the driver's cursors.

The Single-Tier "Lite" Edition OLE DB Provider for ODBC Data Sources uses the provider-specific keyword <code>Cursors</code> in the <code>Extended Properties</code> part of the OLE DB connect string, to control cursor library usage. This keyword can be set to one of three values:  

* {{{ODBC}}}
* {{{Driver}}}
* {{{IfNeeded}}}

Each setting is analogous to the ODBC counterpart SQL_CUR_USE_xxx. The default behavior is {{{Cursors=IfNeeded}}}.

The table below lists the recommended Cursor settings for various ODBC drivers when used with the Single-Tier "Lite" Edition OLE DB Provider for ODBC Data Sources --

| *ODBC Driver* | 	*Cursor setting* | 	*Comments* |
|  All <nop>OpenLink ODBC drivers  |  {{{Driver}}} %BR%or %BR%{{{IfNeeded}}} (default)  | The scrollable cursor support built into our drivers provides the necessary functionality.   |
|  Native Microsoft SQL Server driver  |  {{{ODBC}}}  | The driver's native scrollable cursor support is inadequate.   |