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



You need to change this setting in Access. I think it's one of the
properties on the query when it's in design mode.

Matt 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Douglas W. Palme
Sent: Thursday, July 28, 2005 10:58 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: ODBC Error when importing a LF to Access

It is set to *nomax


On Thu, 28 Jul 2005 08:43:55 -0600, Tyler, Matt wrote
> You have the query governor set up to limit queries to only 60 
> seconds of processing time.  It's probably a System level value
(WRKSYSVAL
> SYSVAL(QQRYTIMLMT)).
> 
> Thank you,
> Matt Tyler
> WinCo Foods, LLC
> mattt@xxxxxxxxxxxxxx
> 
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]
> On Behalf Of Douglas W. Palme
> Sent: Thursday, July 28, 2005 8:39 AM
> To: RPG Group
> Subject: ODBC Error when importing a LF to Access
> 
> We have a LF built on our 400 which we were trying to import to 
> access to verify some data....however when we try to import we are 
> getting the following error message:
> 
> ODBC--call failed.
> 
> [IBM]iSeries Access ODBC Driver][DB2 UDB]SQL666 - Estimated query 
processing
> 
> time 415 exceeds limit 60.
> 
> Any idea what the heck is going on?
> 
> If you bought, it was hauled by a truck - somewhere, sometime.
> 
> --
> 


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.