From: Apostolos B. STERGIOPOULOS <abstergio@hotmail.com>
To: pgsql-interfaces@postgresql.org
Subject: Re: need help with errors in ODBC log
Date: Tue, 27 Mar 2001 16:38:38 -0000
Message-ID: <F181V0mMhBwY486qCsm0000cc4a@hotmail.com> (raw)
=======================
LoginTimeout Property
=======================
Sets or returns the number of seconds before an error occurs when you
attempt to log on to an ODBC database.
Settings and Return Values
~~~~~~~~~~~~~~~~~~~~~~~~~~
The setting or return value is an Integer representing the number of seconds
before a login timeout error occurs.
The default LoginTimeout property setting is 20 seconds. When the
LoginTimeout property is set to 0, no timeout occurs.
Remarks
~~~~~~~
When you're attempting to log on to an ODBC database, such as Microsoft SQL
Server, the connection can fail as a result
of network errors or because the server isn't running. Rather than waiting
for the default 20 seconds to connect, you can
specify how long to wait before raising an error. Logging on to the server
happens implicitly as part of a number of
different events, such as running a query on an external server database.
You can use LoginTimeout on the DBEngine object in both Microsoft Jet and
ODBCDirect workspaces. You can use LoginTimeout
on the Workspace object only in ODBCDirect workspaces. Setting the property
to -1 on a Workspace will default to the current
setting of DBEngine.LoginTimeout. You can change this property in a
Workspace at any time, and the new setting will take
effect with the next Connection or Database object opened.
The default value is determined by the ODBC driver. In a Microsoft Jet
workspace, you can override the drivers default
value by creating a new ODBC key in the Registry path
\HKEY_LOCAL_MACHINE\SOFTWARE\Jet\3.5\, creating a LoginTimeout
parameter in this key, and setting the value as desired.
=======================
QueryTimeout Property
=======================
Sets or returns a value that specifies the number of seconds to wait before
a timeout error occurs when a query is executed
on an ODBC data source.
Settings and Return Values
~~~~~~~~~~~~~~~~~~~~~~~~~~
The setting or return value is an Integer representing the number of seconds
to wait. The default value is 60.
Remarks
~~~~~~~
When you're using an ODBC database, such as Microsoft SQL Server, there may
be delays due to network traffic or heavy use of
the ODBC server. Rather than waiting indefinitely, you can specify how long
to wait.
When you use QueryTimeout with a Connection or Database object, it specifies
a global value for all queries associated with
the database. You can override this value for a specific query by setting
the ODBCTimeout property of the particular QueryDef
object.
In a Microsoft Jet workspace, you can override the default value by creating
a new ODBC key in the Registry path
\HKEY_LOCAL_MACHINE\SOFTWARE\Jet\3.5\, creating a QueryTimeout parameter in
this key, and setting the value as desired.
Attachments:TimeOutProperites.txt (text/plain, 2.7K) download
=======================
LoginTimeout Property
=======================
Sets or returns the number of seconds before an error occurs when you
attempt to log on to an ODBC database.
Settings and Return Values
~~~~~~~~~~~~~~~~~~~~~~~~~~
The setting or return value is an Integer representing the number of seconds
before a login timeout error occurs.
The default LoginTimeout property setting is 20 seconds. When the
LoginTimeout property is set to 0, no timeout occurs.
Remarks
~~~~~~~
When you're attempting to log on to an ODBC database, such as Microsoft SQL
Server, the connection can fail as a result
of network errors or because the server isn't running. Rather than waiting
for the default 20 seconds to connect, you can
specify how long to wait before raising an error. Logging on to the server
happens implicitly as part of a number of
different events, such as running a query on an external server database.
You can use LoginTimeout on the DBEngine object in both Microsoft Jet and
ODBCDirect workspaces. You can use LoginTimeout
on the Workspace object only in ODBCDirect workspaces. Setting the property
to -1 on a Workspace will default to the current
setting of DBEngine.LoginTimeout. You can change this property in a
Workspace at any time, and the new setting will take
effect with the next Connection or Database object opened.
The default value is determined by the ODBC driver. In a Microsoft Jet
workspace, you can override the drivers default
value by creating a new ODBC key in the Registry path
\HKEY_LOCAL_MACHINE\SOFTWARE\Jet\3.5\, creating a LoginTimeout
parameter in this key, and setting the value as desired.
=======================
QueryTimeout Property
=======================
Sets or returns a value that specifies the number of seconds to wait before
a timeout error occurs when a query is executed
on an ODBC data source.
Settings and Return Values
~~~~~~~~~~~~~~~~~~~~~~~~~~
The setting or return value is an Integer representing the number of seconds
to wait. The default value is 60.
Remarks
~~~~~~~
When you're using an ODBC database, such as Microsoft SQL Server, there may
be delays due to network traffic or heavy use of
the ODBC server. Rather than waiting indefinitely, you can specify how long
to wait.
When you use QueryTimeout with a Connection or Database object, it specifies
a global value for all queries associated with
the database. You can override this value for a specific query by setting
the ODBCTimeout property of the particular QueryDef
object.
In a Microsoft Jet workspace, you can override the default value by creating
a new ODBC key in the Registry path
\HKEY_LOCAL_MACHINE\SOFTWARE\Jet\3.5\, creating a QueryTimeout parameter in
this key, and setting the value as desired.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: abstergio@hotmail.com
Subject: Re: need help with errors in ODBC log
In-Reply-To: <F181V0mMhBwY486qCsm0000cc4a@hotmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox