Article ID: 282349 - View products that this article applies to.
This article was previously published under Q282349
Advanced: Requires expert coding, interoperability, and multiuser skills.
This article applies only to a Microsoft Access database (.mdb).
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
When you open a linked Oracle 8ior Sybase table and leave the database inactive for long periods of time, you receive the following error message, and then Access quits:
You may also receive the following error when you try to close the table after long periods of inactivity:
Microsoft Access has encountered a problem and needs to close. We are sorry for any inconvenience.
Clicking Yes results in an endless loop of the error message. To quit Access, you must use Task Manager.
This Action will stop the current code in break mode. Do you want to stop the running code?
This problem occurs when all of the following conditions are true:
To resolve this problem, use one of the following methods.
Method 1: Change the ODBC Refresh Interval Setting
Method 2: Change the ODBC Connection Timeout Setting in the RegistryWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Steps to Reproduce the Behavior
Article ID: 282349 - Last Review: August 10, 2004 - Revision: 5.0