To configure the Microsoft Jet database engine for ODBC access

odbc| Access | data | database
To configure the Microsoft Jet database engine for ODBC access



The following sections describe the Microsoft®windows® registry settings that the Microsoft Jet database engine uses to connect to an ODBC database.



Initialization settings for Microsoft Jet that connects to an ODBC database

The \hkey_local_machine Oftware\microsoft\jet\4.0\engines\odbc folder contains initialization settings for the Microsoft Jet database engine.

Note The following example shows the typical settings for each item in the Jet\4.0\engines\odbc folder.



Logintimeout=20

Querytimeout=60

connectiontimeout=600

asyncretryinterval=500

Attachcasesensitive=0

attachableobjects= ' table ', ' VIEW ', ' SYSTEM TABLE ', ' ALIAS ', ' synonym '

Snapshotonly=0

Tracesqlmode=0

Traceodbcapi=0

Disableasync=1

Tryjetauth=1

Preparedinsert=0

Preparedupdate=0

Fastrequery=0

Fatblastrows=-1

Fatblasttimeout=3

Odbcisamattach=0



The Microsoft Jet database engine uses the ODBC entry shown below.



Item

Description

LoginTimeout

The number of seconds that a logon attempt can last before timing out. The default value is 20 (the value is REG_DWORD type).

QueryTimeout

The number of seconds (total processing time) that the query can run before it times out. If disableasync=0 (the default), QueryTimeout is the number of seconds that are required to wait for the server to respond when each polling query completes. The default value is 60 (the value is REG_DWORD type).

ConnectionTimeout

The number of seconds that a cached connection can remain idle before timing out. The default value is 600 (the value is REG_DWORD type).

Asyncretryinterval

The number of milliseconds between rounds that determine whether the server has completed query processing. This entry is for asynchronous processing only. The default value is 500 (the value is REG_DWORD type).

Attachcasesensitive

Indicator to determine whether the table name matches exactly when linked. A value of 0 (a link to the first table that matches the specified name, regardless of case) and 1 (linked table only when the name exactly matches). The default value is 0 (the value is REG_DWORD type).

Attachableobjects

A list of server object types that are allowed to link to them. The default values are: Table, VIEW, SYSTEM TABLE, ALIAS, synonym (value is REG_SZ type).

SnapshotOnly

Indicator to determine whether to force the Recordset object to be a snapshot type. The value is 0 (allow dynaset) and 1 (Force snapshot). The default value is 0 (the value is REG_DWORD type).

TraceSQLMode

Indicator to determine whether the Microsoft Jet database engine Tracks SQL statements sent to an ODBC data source in SQLOUT.txt. The value is 0 (no) and 1 (yes). The default value is 0 (the value is REG_DWORD type). This item can be exchanged with Sqltracemode.

Traceodbcapi

Indicator to determine whether to track ODBC API calls in ODBCAPI.txt. The value is 0 (no) and 1 (yes). The default value is 0 (the value is REG_DWORD type).

Disableasync

Indicator to determine whether to force a synchronous query. Value is 0 (use asynchronous query execution if possible) and 1 (Enforce synchronous query). The default value is 1 (the value is REG_DWORD type).

TryJetAuth

Indicator to determine whether to try to log on to the server using a Microsoft Access username and password before you are prompted. The value is 0 (no) and 1 (yes). The default value is 1 (the value is REG_DWORD type).

Preparedinsert

Indicator to determine whether to insert data into all columns using a prepared INSERT statement. A value of 0 (using a custom INSERT statement that inserts a non-Null value only) and 1 (using a prepared INSERT statement). The default value is 0 (the value is REG_DWORD type).

Using a prepared INSERT statement can cause Null to overwrite the server defaults, and can cause triggers to be executed against columns that are not explicitly inserted.

Preparedupdate

Indicator to determine whether to update the data in all columns with the prepared UPDATE statement. A value of 0 (using a custom UPDATE statement that sets only the changed columns) and 1 (using the prepared UPDATE statement). The default value is 0 (the value is REG_DWORD type).

Using a prepared UPDATE statement causes the trigger to execute against the unchanged column.

Fastrequery

Indicator to determine whether to use a prepared SELECT statement for a parameterized query. The value is 0 (no) and 1 (yes). The default value is 0 (the value is REG_DWORD type).

Fatblastrows



Fatblasttimeout



Odbcisamattach





Note When you change the Windows registry settings, you must exit the database engine before restarting it so that the new settings will not take effect.

Note: from MSDN