Returns the cursor type used. This parameter can correspond to one or more of the following constants:

Cursor location
hClientCursor	Cursor managed by MDAC. Generally, it offers more features than a server-side cursor. A client-side cursor is always static.
hServerCursor	Cursor managed by the database. This cursor can easily reflect changes made to data by other users.
Cursor type
hDynamicCursor	This cursor offers many features, but consumes a lot of memory. This cursor supports all types of scrolling. You can access all insert, update and delete operations made by other users.
hForwardOnlyCursor	This cursor is fast and consumes little memory. The cursor can only move forward and be scrolled from the first to the last record. Changes made by other users are not visible.
hOpenKeysetCursor	This cursor handles a fixed set of records. Only the key of each record is stored and not the actual record (consumes less memory). Deleted records cannot be accessed. Changes made by other users are visible (but added records are not).
hStaticCursor	Makes a copy of all query records in memory (high memory consumption). All types of scrolling are supported.
Lock modes
hReadOnlyCursor	The record set manipulated cannot be modified.
hOptimisticCursor	The record is locked when it is updated
hPessimisticCursor	The record is locked as soon as it is edited.

Remark: If no constant was specified in HDescribeConnection, this parameter is set to 0.

Caution: some types of cursors may not be supported by all the OLE DB providers.

• Name of the data file used. This name was defined in the data model editor or with the File Description type.
• Name of the connection used. This name was defined in the data model editor, or with HDescribeConnection or HOpenConnection.