× 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.


  1.  Home
  2. MIDRANGE-L
  3. October 2002

SQL ODBC Timer

Hi everyone,

I've got a Visual Basic program that connects to my AS/400 data using the
Client Access ODBC driver. The users get to essentially build their own
query by choosing from a list of options and then the program runs an SQL
statement to return the results.

Sometimes, they get a message saying that the CA ODBC time limit of 30 has
been exceeded, and the query doesn't run. I've been able to fix this so
far by building LFs over the files being used, but I'm curious -- does
anyone know where this time limit comes from and (more importantly)
whether it can be changed? If it _can_ be changed, are there any
suggestions (beyond trial and error) for deciding what an appropriate
value should be?

TIA,

Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@juddwire.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.