Larry W Jordan Jr.
Derik Harris
Microsoft Corporation
Created: July 15, 1996
Revised: August 7, 1996
Larry W Jordan Jr. is a Senior Microsoft Access support engineer. His main focus is VBA, wizard and add-in development and Visual SourceSafe integration.
Derik Harris is a Senior Microsoft Access content engineer. His primary responsibility is writing, editing, and publishing Microsoft Access related material for the Microsoft Knowledge Base and the Microsoft Web site.
Click to open or copy the ODBCREG project files.
The ODBC Registry Wizard automates the management of the registry entries associated with the Microsoft Jet database engine. These entries are commonly referred to as “Initializing the Microsoft ODBC Database Driver.” These entries aid developers and support personnel who troubleshoot the issues involved with using ODBC access to external database applications.
These entries are not created by any application by default, including Microsoft Access. In order to make use of these parameters, the entries must exist in the operating system registry before starting the application that you intend to use for troubleshooting.
The additional purpose of the wizard is to make it easy for developers to include this level of troubleshooting support in the applications they ship, based upon Microsoft Access for Windows 95 version 7.0.
The number of seconds a login attempt can continue before timing out. The default is 20 (values are of type REG_DWORD).
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | LoginTimeout |
| KEY TYPE: | REG_DWORD |
| DEFAULT VALUE: | 20 |
The number of seconds a query can run (total processing time) before timing out. The default is 60 (values are of type REG_DWORD).
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | QueryTimeout |
| KEY TYPE: | REG_DWORD |
| DEFAULT VALUE: | 60 |
The number of seconds a cached connection can remain idle before timing out. The Default is 600 (values are of type REG_DWORD).
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | ConnectionTimeout |
| KEY TYPE: | REG_DWORD |
| DEFAULT VALUE: | 600 |
The number of milliseconds between polls to determine if the server is finished processing a query. This entry is used for asynchronous processing only. The default is 500 (values are of type REG_DWORD).
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | AsyncRetryInterval |
| KEY TYPE: | REG_DWORD |
| DEFAULT VALUE: | 500 |
An indicator of whether to match table names exactly when linking. Values are 0 (link the first table matching the specified name, regardless of case) and 1 (link a table only if the name matches exactly). The default is 0 (values are of type REG_DWORD).
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | AttachCaseSensitive |
| KEY TYPE: | REG_DWORD |
| DEFAULT VALUE: | 0 |
A list of server object types to which linking will be allowed. The default is 'TABLE', 'VIEW', 'SYSTEM TABLE', 'ALIAS', 'SYNONYM' (values are of type REG_SZ).
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | AttachableObjects |
| KEY TYPE: | REG_SZ |
| DEFAULT VALUE: | 'TABLE', 'VIEW', 'SYSTEM TABLE', 'ALIAS', 'SYNONYM' |
An indicator of whether Recordset objects are forced to be of snapshot type. Values are 0 (allow dynasets) and 1 (force snapshots only). The default is 0 (values are of type REG_DWORD).
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | SnapshotOnly |
| KEY TYPE: | REG_DWORD |
| DEFAULT VALUE: | 0 |
An indicator of whether the Microsoft Jet database engine will trace SQL statements sent to an ODBC data source in SQLOUT.txt. Values are 0 (no) and 1 (yes). The default is 0 (values are of type (REG_DWORD). This entry is interchangeable with SQLTraceMode.
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | TraceSQLMode |
| KEY TYPE: | REG_DWORD |
| DEFAULT VALUE: | 0 |
An indicator of whether to trace ODBC API calls in ODBCAPI.txt. Values are 0 (no) and 1 (yes). The default is 0 (values are of type REG_DWORD).
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | TraceODBCAPI |
| KEY TYPE: | REG_DWORD |
| DEFAULT VALUE: | 0 |
An indicator of whether to force synchronous query execution. Values are 0 (use asynchronous query execution if possible) and 1 (force synchronous query execution). The default is 0 (values are of type REG_DWORD).
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | DisableAsync |
| KEY TYPE: | REG_DWORD |
| DEFAULT VALUE: | 0 |
An indicator of whether to try using the Microsoft Access user name and password to log in to the server before prompting. Values are 0 (no) and 1 (yes). The default is 1 (values are of type REG_DWORD).
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | JetTryAuth |
| KEY TYPE: | REG_DWORD |
| DEFAULT VALUE: | 1 |
An indicator of whether to use a prepared INSERT statement that inserts data in all columns. Values are 0 (use a custom INSERT statement that inserts only non-Null values) and 1 (use a prepared INSERT statement). The default is 0 (values are of type REG_DWORD). Using prepared INSERT statements can cause Nulls to overwrite server defaults and can cause triggers to execute on columns that weren't inserted explicitly.
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | PreparedInsert |
| KEY TYPE: | REG_DWORD |
| DEFAULT VALUE: | 1 |
An indicator of whether to use a prepared UPDATE statement that updates data in all columns. Values are 0 (use a custom UPDATE statement that sets only columns that have changed) and 1 (use a prepared UPDATE statement). The default is 0 (values are of type REG_DWORD). Using prepared UPDATE statements can cause triggers to execute on unchanged columns.
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | PreparedUpdate |
| KEY TYPE: | REG_DWORD |
| DEFAULT VALUE: | 0 |
An indicator of whether to use a prepared SELECT statement for parameterized queries. Values are 0 (no) and 1 (yes). The default is 0 (values are of type REG_DWORD)
Parameter Details
| HKEY LOCATION: | Software\Microsoft\Jet\3.0\Engines\ODBC |
| KEY VALUE: | FastRequery |
| KEY TYPE: | REG_DWORD |
| DEFAULT VALUE: | 0 |
The Windows Registry can be used to tune the operation of the ODBC driver. If your application can't accept the default behavior of the drivers, the ODBC Registry Wizard makes it easy to override the default settings to get the appropriate behavior from your application.