WINDEV, WEBDEV AND WINDEV MOBILEONLINE HELP
Version: 1516171819202122232425
Finding out the type of cursor Hide the details
Returns the type of cursor used. This parameter can correspond to one or more of the following constants:Location of cursorshClientCursorCursor managed by MDAC. Offers more features than a server cursor. A client cursor must necessarily be a static cursor.hServerCursorCursor managed by the database. This cursor can easily apply the changes performed by the other users to the data.Type of cursorhDynamicCursorCursor offering a lot of features but consuming a lot of memory. This cursor allows all types of moves. It allows you to access all the modifications, additions and deletions performed by the other users.hForwardOnlyCursorFast cursor consuming little memory. The move is performed from the first record to the last one. The data modified by the other users is not visible.hOpenKeysetCursorCursor that handles a fixed set of records. Only the keys corresponding to the record are stored and not the records (consumes less memory). The deleted records can no longer be accessed. The modifications performed by the other users are visible (but not the additions).hStaticCursorRetrieves a copy of all the query records in memory (consumes a lot of memory). All types of moves are allowed.Lock modeshReadOnlyCursorThe set of records cannot be modified.hOptimisticCursorThe record is locked when it is updatedhPessimisticCursorThe record is locked as soon as it becomes in edit to be modified.Note: If no constant was specified in HDescribeConnection or in the connection, this parameter is set to 0.Caution: Some types of cursors may not be supported by all the OLE DB providers or by all the native accesses.
Name of connection used. This name was defined:in the data model editor, by HDescribeConnection or HOpenConnection, by the Connection type.
Modifying the type of cursor Hide the details
Returns the type of cursor used. This parameter can correspond to one or more of the following constants:Location of cursorshClientCursorCursor managed by MDAC. Offers more features than a server cursor. A client cursor must necessarily be a static cursor.hServerCursorCursor managed by the database. This cursor can easily apply the changes performed by the other users to the data.Type of cursorhDynamicCursorCursor offering a lot of features but consuming a lot of memory. This cursor allows all types of moves. It allows you to access all the modifications, additions and deletions performed by the other users.hForwardOnlyCursorFast cursor consuming little memory. The move is performed from the first record to the last one. The data modified by the other users is not visible.hOpenKeysetCursorCursor that handles a fixed set of records. Only the keys corresponding to the record are stored and not the records (consumes less memory). The deleted records can no longer be accessed. The modifications performed by the other users are visible (but not the additions).hStaticCursorRetrieves a copy of all the query records in memory (consumes a lot of memory). All types of moves are allowed.Lock modeshReadOnlyCursorThe set of records cannot be modified.hOptimisticCursorThe record is locked when it is updatedhPessimisticCursorThe record is locked as soon as it becomes in edit to be modified.Caution: Some types of cursors may not be supported by all the OLE DB providers or by all the native accesses.
Last update: 10/31/2019
Send a report | Local help
Searching...
J'accepte les termes de la licence
All you have to do is configure your product as follows: