(DM) f90SQLBrowseConnect was called for the ConnectionHandle and returned SQL_NEED_DATA. This function was called before f90SQLBrowseConnect returned SQL_SUCCESS_WITH_INFO or SQL_SUCCESS.

SQL_MODE_READ_ONLY is used by the driver or data source as an indicator that the connection is not required to support SQL statements that cause updates to occur. This mode can be used to optimize locking strategies, transaction management, or other areas as appropriate to the driver or data source. The driver is not required to prevent such statements from being submitted to the data source. The behavior of the driver and data source when asked to process SQL statements that are not read-only during a read-only connection is implementation-defined.

SQL_MODE_READ_WRITE is the default.

SQL_ASYNC_ENABLE_OFF = Off (the default)

SQL_ASYNC_ENABLE_ON = OnSetting

SQL_ASYNC_ENABLE_ON enables asynchronous execution for all future statement handles allocated on this connection. It is driver-defined whether this enables asynchronous execution for existing statement handles associated with this connection. An error is returned if asynchronous execution is enabled while there is an active statement on the connection. This attribute can be set whether f90SQLGetInfo with the SQL_ASYNC_MODE information type returns SQL_AM_CONNECTION or SQL_AM_STATEMENT.

After a function has been called asynchronously, only the original function, f90SQLAllocHandle, f90SQLCancel, f90SQLGetDiagField, or f90SQLGetDiagRec can be called on the statement or the connection associated with StatementHandle, until the original function returns a code other than SQL_STILL_EXECUTING. Any other function called on StatementHandle or the connection associated with StatementHandle returns SQL_ERROR with an SQLSTATE of HY010 (Function sequence error). Functions can be called on other statements.

In general, applications should execute functions asynchronously only on single-thread operating systems. On multithread operating systems, applications should execute functions on separate threads, rather than executing them asynchronously on the same thread. Drivers that operate only on multithread operating systems do not need to support asynchronous execution.

The following functions can be executed asynchronously:

f90SQLBulkOperations, f90SQLColAttribute, f90SQLColumnPrivileges, f90SQLColumns, SQLCopyDesc, f90SQLDescribeCol, f90SQLDescribeParam, f90SQLExecDirect, f90SQLExecute, f90SQLFetch, f90SQLFetchScroll, f90SQLForeignKeys, f90SQLGetData f90SQLGetDescField [1], f90SQLGetDescRec[ 1], f90SQLGetDiagField, f90SQLGetDiagRec, f90SQLGetTypeInfo, f90SQLMoreResults, f90SQLNumParams, f90SQLNumResultCols, f90SQLParamData, f90SQLPrepare, f90SQLPrimaryKeys, f90SQLProcedureColumns, f90SQLProcedures, f90SQLPutData, f90SQLSetPos, f90SQLSpecialColumns, f90SQLStatistics, f90SQLTablePrivileges, f90SQLTables

[1] These functions can be called asynchronously only if the descriptor is an implementation descriptor, not an application descriptor

SQL_TRUE = Automatic population of the IPD after a call to f90SQLPrepare is supported by the driver.

SQL_FALSE = Automatic population of the IPD after a call to f90SQLPrepare is not supported by the driver.

Servers that do not support prepared statements will not be able to populate the IPD automatically. If SQL_TRUE is returned for the SQL_ATTR_AUTO_IPD connection attribute, the statement attribute SQL_ATTR_ENABLE_AUTO_IPD can be set to turn automatic population of the IPD on or off. If SQL_ATTR_AUTO_IPD is SQL_FALSE, SQL_ATTR_ENABLE_AUTO_IPD cannot be set to SQL_TRUE. The default value of SQL_ATTR_ENABLE_AUTO_IPD is equal to the value of SQL_ATTR_AUTO_IPD.This connection attribute can be returned by f90SQLGetConnectAttr, but cannot be set by f90SQLSetConnectAttr.

SQL_AUTOCOMMIT_OFF = The driver uses manual-commit mode, and the application must explicitly commit or roll back transactions with

f90SQLEndTran.SQL_AUTOCOMMIT_ON = The driver uses auto-commit mode. Each statement is committed immediately after it is executed. This is the default. Any open transactions on the connection are committed when SQL_ATTR_AUTOCOMMIT is set to SQL_AUTOCOMMIT_ON to change from manual-commit mode to auto-commit mode.

For more information, see the SQL_CURSOR_COMMIT_BEHAVIOR and SQL_CURSOR_ROLLBACK_BEHAVIOR information types in f90SQLGetInfo

When a batch is executed in autocommit mode, two things are possible. The entire batch can be treated as an autocommitable unit, or each statement in a batch is treated as an autocommitable unit. Certain data sources may support both these behaviors and may provide a way of choosing one or the other. It is driver-defined whether a batch is treated as an autocommitable unit, or whether each individual statement within the batch is autocommitable.

If SQL_TRUE, the string argument of catalog functions are treated as identifiers. The case is not significant. For non-delimited strings, the driver removes any trailing spaces, and the string is folded to uppercase. For delimited strings, the driver removes any leading or trailing spaces, and takes literally whatever is between the delimiters. If one of these arguments is set to a null pointer, the function returns SQL_ERROR and SQLSTATE HY009 (Invalid use of null pointer).

If SQL_FALSE, the string arguments of catalog functions are not treated as identifiers. The case is significant. They can either contain a string search pattern or not, depending on the argument. The default value is SQL_FALSE.

The TableType argument of f90SQLTables, which takes a list of values, is not affected by this attribute. SQL_ATTR_METADATA_ID can also be set on the statement level. (It is the only connection attribute that is also a statement attribute.)

SQL_CUR_USE_IF_NEEDED = The Driver Manager uses the ODBC cursor library only if it is needed. If the driver supports the SQL_FETCH_PRIOR option in f90SQLFetchScroll, the Driver Manager uses the scrolling capabilities of the driver. Otherwise, it uses the ODBC cursor library.

SQL_CUR_USE_ODBC = The Driver Manager uses the ODBC cursor library.SQL_CUR_USE_DRIVER = The Driver Manager uses the scrolling capabilities of the driver. This is the default setting.

Note: Many data sources either do not support this option or can only return the network packet size.

If the specified size exceeds the maximum packet size or is smaller than the minimum packet size, the driver substitutes that value and returns SQLSTATE 01S02 (Option value changed).

If the application sets packet size after a connection has already been made, the driver will return SQLSTATE HY011 (attribute cannot be set now).

The driver uses this handle to display dialog boxes.

Note: The SQL_ATTR_QUIET_MODE connection attribute does not apply to dialog boxes displayed by f90SQLDriverConnect.

SQL_OPT_TRACE_OFF = Tracing off (the default)

SQL_OPT_TRACE_ON = Tracing on. When tracing is on, the Driver Manager writes each ODBC function call to the trace file.

Note: When tracing is on, the Driver Manager can return SQLSTATE IM013 (Trace file error) from any function.

An application specifies a trace file with the SQL_ATTR_TRACEFILE option. If the file already exists, the Driver Manager appends to the file. Otherwise, it creates the file. If tracing is on and no trace file has been specified, the Driver Manager writes to the file SQL.LOG in the root directory.

An application can set the variable ODBCSharedTraceFlag to enable tracing dynamically. Tracing is then enabled for all ODBC applications currently running. If an application turns tracing off, it is turned off only for that application. If the Trace keyword in the system information is set to 1 when an application calls f90SQLAllocHandle with a HandleType of SQL_HANDLE_ENV, tracing is enabled for all handles. It is enabled only for the application that called f90SQLAllocHandle.

Calling f90SQLSetConnectAttr with an Attribute of SQL_ATTR_TRACE does not require that the ConnectionHandle argument be valid, and will not return SQL_ERROR if ConnectionHandle is NULL. This attribute applies to all connections.

Calling f90SQLSetConnectAttr with an Attribute of SQL_ATTR_ TRACEFILE does not require the ConnectionHandle argument to be valid, and will not return SQL_ERROR if ConnectionHandle is invalid. This attribute applies to all connections.

This option may be specified only if the driver has connected to the data source. The setting of this attribute will persist across connections.

program TraceExample

 

!load f90SQL modules

use f90SQLConstants

use f90SQL

 

implicit none

integer(SQLHENV_KIND)::EnvHndl

integer(SQLHDBC_KIND)::ConnHndl

integer(SQLHSTMT_KIND):: StmtHndl

integer(SQLRETURN_KIND):: iRet

integer:: i

 

!allocate an environment handle

call f90SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, EnvHndl, iRet)

 

!Set ODBC version we will be using (3.x in this case)

call f90SQLSetEnvAttr(EnvHndl, SQL_ATTR_ODBC_VERSION, SQL_OV_ODBC3, iRet)

 

!Allocate a connection handle

call f90SQLAllocHandle(SQL_HANDLE_DBC,EnvHndl, ConnHndl, iRet)

 

!set the name of the trace file

call f90SQLSetConnectAttr(ConnHndl, SQL_ATTR_TRACEFILE, 'c:\test.log', iRet)

!enable tracing

call f90SQLSetConnectAttr(ConnHndl, SQL_ATTR_TRACE, SQL_OPT_TRACE_ON, iRet)

 

!Open DSN BookSales

call f90SQLConnect(ConnHndl,'BookSales','Admin','',iRet)

....

....

....