Scrollable cursors allow applications to set the current position of the cursor anywhere in the resultset by specifying appropriate scrolling options. Applications can use one of NEXT, PRIOR, FIRST, LAST, RELATIVE, or ABSOLUTE scrolling options to traverse the resultset as desired.
When scrollable cursors are requested, either a server-side or client-side scrollable cursor may be invoked. Adaptive Server must support scrollable cursors in order for a server-side cursor to be invoked. If Adaptive Server does not support scrollable cursors, the desired functionality may be mimicked by the driver using cached resultset. This is known as client-side scrollable cursors.
The ASE ODBC Driver and the ASE OLE DB Provider can support both server-side and client-side scrollable cursors on ASE version 15.0 and later. But only client-side scrollable cursors are supported on all pre-15.0 ASE versions.
The UseCursor property must be set correctly in order to obtain the desired scrollable cursor.
WARNING! Client-side scrollable cursors use more memory on the client side and may generate higher network traffic.
How you set the UseCursor connection property determines whether client-side or server-side scrollable cursors are used:
When you set the UseCursor connection property to 1, and the ASE version is 15.0 or later, server-side scrollable cursors are used.
Server-side scrollable cursors are not available on
all pre-15.0 ASE versions.
When you set the UseCursor connection property to 0, client-side scrollable cursors (cached resultsets) are used, regardless of the ASE version.
