× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



At 07:00 PM 9/4/97 -0700, George Hughen <ghughen@tsidss.com> wrote:

>I am trying to find out how to overcome a problem that I am having when
>trying to run a certain SQL statement from a VB program via ODBC.
>I get the error message: SQL0666, which reads: 
>       Estimated query processing time 31 exceeds limit 30.
>
>       (This also occurs in the job log of the QZDASOINIT job as CPF427F)
>
>This indicates that the server job somehow changes its time limit to 
>30 seconds using the CHGQRYA CL command (or possibly by some
>other method).
>
>Incidentally, the query only takes 1 second when run using interactive SQL.
>So much for the predictive query governor!

George

The same thing happened to me some time ago. Actually, the timeouts are set
in VB (or MS Access), either with the ODBCTimeOut property or the
QueryTimeOut property. It's been a while-I don't remember which one does
the job.  Anyway, here's WinHelp for both:

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
ODBCTimeout Property (Microsoft Access)

You can use the ODBCTimeout property to specify the number of seconds
Microsoft Access waits before a time-out error occurs when a query is run
on an Open Database Connectivity (ODBC) database.

Setting

The ODBCTimeout property is an Integer value representing the number of
seconds Microsoft Access waits. The default is 60 seconds. When this
property is set to 0, no timeout occurs.
You can set this property in the property sheet in the Query window or
Visual Basic.

Remarks

When you're using an ODBC database, such as an Microsoft SQL Server, there
may be delays due to network traffic or heavy use of the ODBC server. The
ODBCTimeout property lets you specify how long Microsoft Access waits for a
network connection before a time-out error occurs.
When the ODBCTimeout property is set to zero, no time-out errors occur.

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
QueryTimeout Property

Sets or returns a value that specifies the number of seconds the Microsoft
Jet database engine waits before a timeout error occurs when a query is
executed on an ODBC database.

Settings and Return Values

The setting or return value is an integer representing the number of
seconds the Jet database engine waits before timing out and returning an
error. The data type is Integer.

Remarks

When you're using an ODBC database, such as 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 before the Jet database
engine produces an error.
When used with a Database object, the QueryTimeout property specifies a
global value for all queries associated with the database.
The timeout value is taken from the Windows Registry. If there is no
Windows Registry setting, the default value is 60 seconds. Once this
property is set, however, it overrides any Windows Registry setting or
default value.

Good luck

Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN 55401
(612) 371-1111 x480
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.