I also get that error periodically when using stored queries in Access
(still using 3.34 (2.71TC3) driver in most cases, but started getting it
more and more after Office updates and security patches are getting
applied). The default 'ODBC Timeout' is set at 60 and can be viewed/changed
by looking at the properties of the query. If I get this error, I usually
just change it to 0 as I want it to run, but could hang Access as well (I
can live with having to kill Access every now and then to not have my query
fail every time)
Thanks,
Randy
-----Original Message-----
From: fprose@hotmail.com [mailto:fprose@hotmail.com]
Sent: Monday, November 03, 2003 9:17 AM
To: informix-list@iiug.org
Subject: Access 2002 ODBC Timeout Issue
Desktop PC was recently upgraded (replaced would be a better term)
with Access 2002 XP version and Informix SDK 2.81. This installs ODBC
3.82.
An Access application that performed query's against Sysmaster (using
links to systabnames and sysptnhdr) for statistics gathering now fails
with an ODBC error:
[Informix][Informix ODBC Driver]Timeout expired.
(#-11094)[Informix][Informix ODBC Driver][Informix]Statement
interrupted by user. (#-213)
The ODBC connection test's ok and opening the link's to systabnames
and sysptnhdr individually returns data with no issues.
No changes have been made to the server.
Checking the IBM/Informix defects list didn't show anything.
Any suggestions?
Thanks,
Fred Prose
Az Supreme Court
sending to informix-list