SQLFetchActivatesBuffer - cSQLStatement
Connect or disconnect a file buffer to a statement result set.
Type: Procedure
Parameters
| Parameter | Type | Description |
|---|---|---|
| iFileNum | Integer | Table whose file buffer to connect to |
| bState | Integer | Buffer state |
Syntax
Procedure SQLFetchActivatesBuffer Integer iFileNum Integer bState
Call Example
Send SQLFetchActivatesBuffer iFileNum bState
Description
If bState is true, the message will setup a buffer so its DF_FILE_STATUS file attribute is set to DF_FILE_ACTIVE when the SQLFetch message is called for this statement. This message only handles the status of the buffer; to bind a buffer to a statement you must use SQLBindFile.
If bState is false, the status of the buffer will no longer be set when SQLFetch is called. The binding that may exist will not be removed. To bind a buffer to a statement use SQLBindFile.
Setting up a buffer to be activated in this way will interfere with internal Connectivity Kit optimization logic. Make sure to switch off the behavior as soon as it is no longer needed.
There is no check if the statement contains columns of the buffer in question! It is not possible to bind a buffer of a different type than the Connectivity Kit in use. You cannot use SQLFetchActivatesBuffer to activate a DataFlex buffer from a SQL Server statement.