ODBCOPTIONS table

Major version number of the ODBC driver / server (read only).

Minor version (read only).

Revision number (read only).

Build number (read only).

The name of the configuration including full path (read only).

The report directory of the configuration (read only).

1 if the loaded configuation is also the active configuration, 0 otherwise (read only).

The number of current connections to the ODBC server (0 for stand alone driver) (read only).

While 0, the ODBC server accepts connections, if set to 1, no more connections are allowed until set 0 again.

If 1, the ODBC server will shut down if requested, killing active connections. If set 0, the ODBC server refuses to shut down while connections are open. This value is saved across runs.

(Stand-alone driver only) If this value is 1, the driver will terminate the DAO engine when unloaded. This is a problem for applications that either themselves use DAO (like MSAccess) or load and unload the ODBC driver several times (like Definition using the new graph ActiveX). In general, it is recommended to use the stand-alone driver ONLY for your own simple applications that are NOT MSAccess applications. This value is saved across runs.

If this value is set to 1, the configuration is closed each time the LAST table using the configuration is closed for each connection. This will free some memory and allow for other applications to change the configuration so that the driver will see these changes the next time it opens a table without having to be restarted (IF all tables are closed while the other application makes its changes, of course). However, it will slow down the driver as it will have to load the configuration again, when tables are again opened. If the value is 0, the configuration is kept loaded in the driver (from the moment the first table is opened) until the driver is unloaded (or actually until the connection is closed), and changes made by Definition will be overwritten if the driver needs to write more changes. This value is saved across runs.

For the purpose of performance improvements in ODBC, the ODBC Server is now allowed to keep the configuration open indefinitely after first use. This means that a subsequent connection to the ODBC Server will be faster as the configuration is already loaded.

Note that when this option is set, only a single connection is allowed at any time to the ODBC Server. If several connections already exist when you attempt to apply the option, it will fail until all other connections are closed. Note also that since the configuration is always loaded, changes to the configuration from outside ODBC is not detected by the ODBC Server, until it is restarted, or NEVERFREE is set to 0 in the ODBCOPTIONS table.

This option is also available in the Windows Registry as "HKEY_CURRENT_USER\Software\7-Technologies\IGSS32\V8.00.00\ODBCDriver_HKLM\NeverFree", which is DWORD set to 0 or 1

Where 1 means that the configuration should never be unloaded.

1 if a table related to the configuration file or descriptor file is open, 0 if not (read only).

If 0 (default), the relevant configuration files are saved each time an update is performed. If set to 1, the configuration files are not saved until this field is reset to 0 or the ODBC connection is shut down (the application closes). This feature may enhance performance, but may also make the ODBC driver more vulnerable to power failures and system crashes. When 1, it will overrule FREEONCLOSE and behave as if FREEONCLOSE is 0.

1 if everything has been saved, 0 if some files still needs to be saved (set NOSAVE to 0 to save everything) (read only).