- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsHello all,
I have an Access 2k db that uses a Pervasive (SQL V8 SP1) connection to an accounting package. The tables from the accounting application contain invoice transactions with lots of histroy records. I now get the following error when running a query in Access that will use these tables. If I use smaller tables I will not get the error.
3146 ODBC - call failed
[ODBC Engine Interface] S1T00 Timeout expired
Is there a way to increase the Timeout and if so where is this property stored??
Thanks,
ET
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: mirtheilPosted on 2006-01-13 at 16:43:25ID: 15697575
I believe the Linked Table Properties has a Timeout value that can be set within Access.
E\ODBC\ODB C.INI\<dsn name>\
You can also change it at the DSN level. From the Pervasive KB (article psql3973):
another solution is to change the environment to make the Pervasive.SQL V8 engine to ignore the timeout setting. This is a "Datasource Name" setting, the setting is specific to a client DSN . Connections to different DSNs but to the same database or engine DSN may have different behavior.
The DSN entry is:
HKEY_LOCAL_MACHINE\SOFTWAR
2. Under this entry, create a new string value named: QueryTimeOutAllowed
3. Set the value to NO to ignore any query timeouts. Set the value to YES to timeout.
If set to "YES", the engine enforces query timeouts for all connections to that DSN. If the setting is set to "NO", the engine ignores any query timeouts for connections to the given DSN.
The default behavior is as if the setting was set to "YES".