There are several Timeout areas to look at, depending on whether a 16 or 32
bit driver is being used.

If 32 bit drivers are being used, and Jet 3.5 is being used as the Database
Engine on the client, then look at:

HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\3.5\Engines\ODBC\

There are a variety of values in there which can be modified, such as:
  ConnectionTimeout
  QueryTimeout

and in

HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\3,5\Engines\Jet3.5\

  Threads (increase from the default of 3 to handle more background data)
  FlushTransactionTimeout (increase from the default of 500 on a slow WAN)

These and other settings are documented in the Microsoft Knowledge Base on
the Microsoft Site under "Developers"  Use any of the Keys as a search item.

Best Regards,
Joe


> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Reiner Hutsch
> Sent: Wednesday, March 04, 1998 3:03 PM
> To: [log in to unmask]
> Subject: ODBC Timeout
>
>
> Hi all,
> two weeks ago David N. Lukenbill posted a question concerning ODBC
> timeouts.
> Yu-Hsin Seah answered to insert "CommitTimeout" into
> HKEY_CURRENT_USER\Software\ODBC\ODBC.INI.
> But where must this key be specified (below ODBC.INI or below each data
> source)? Which kind of value (string, binary or dword)?.
>
> Thanks for your help,
> Reiner Hutsch
>
> +--------------------------+-----------------------+
> | Reiner Hutsch            | [log in to unmask] |
> +--------------------------+-----------------------+
> | IMW-KOELN                | Stadtwaldguertel 33   |
> | Phone: +49 221 940566-21 | 50935 Koeln           |
> | Fax: +49 221 407300      | Germany               |
> +--------------------------+-----------------------+
>