Share via

"ODBC call failed"

Anonymous
2016-11-28T14:14:11+00:00

I keep getting and error running a query in Microsoft Access 2007

"ODBC call failed"  [Informix][Informix ODBC Driver] Timeout expired (#-11094)  [Informix][Informix ODBC Driver] Statement interrupted by user. (#-213)" 

 It only happens when I query large sets of data. If I filter data to small amounts the query returns my results with no error.  Why can't I return large amounts of data? Seems like the server I am connecting to is breaking off the connection.

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

6 answers

Sort by: Most helpful
  1. Tom van Stiphout 40,211 Reputation points MVP Volunteer Moderator
    2016-11-28T21:49:04+00:00

    That depends on what library you're using to connect to the database. Are you using ADO or DAO? Each has a slightly different way to do it. Use the Object Browser (F2) and search the library for "timeout".

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-11-28T18:11:29+00:00

    Where do you adjust the timeout in Access 2007? I tried in the Access Options section but nothing happened. Then I read it had to be done somewhere in the registry?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-11-28T16:55:29+00:00

    Hi,

    I don't use Informix but DB2 (via ODBC). For same problems I use PassThrough queries.

    Ciao Mimmo

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-11-28T16:17:19+00:00

    Thanks Tom!  I will give that a try

    Was this answer helpful?

    0 comments No comments
  5. Tom van Stiphout 40,211 Reputation points MVP Volunteer Moderator
    2016-11-28T15:42:51+00:00

    That would be a good question for an Informix forum.

    Why don't you believe the error message: it's taking too long to run your query given the connection settings that are in play. You may want to increase the connection timeout.

    Was this answer helpful?

    0 comments No comments