BUG: Access quits unexpectedly when linked Oracle table is left inactive

This article was previously published under Q282349
This article has been archived. It is offered "as is" and will no longer be updated.
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:
256986 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:
Microsoft Access has encountered a problem and needs to close. We are sorry for any inconvenience.
You may also receive the following error when you try to close the table after long periods of inactivity:
This Action will stop the current code in break mode. Do you want to stop the running code?
Clicking Yes results in an endless loop of the error message. To quit Access, you must use Task Manager.
This problem occurs when all of the following conditions are true:
  • You are using the Microsoft for Oracle driver, version 2.573.6526.00.
  • You have the ODBC Refresh Interval set to 1500.
  • You have the ODBC ConnectionTimeout registry setting set to something other than 0.
To resolve this problem, use one of the following methods.

Method 1: Change the ODBC Refresh Interval Setting

  1. Start Microsoft Access.
  2. On the Tools menu, click Options.
  3. Click the Advanced tab.
  4. Change the ODBC Refresh Interval setting to a value greater than the default setting of 1500.

Method 2: Change the ODBC Connection Timeout Setting in the Registry

WARNING: 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.
  1. On the Start Menu, click Run.
  2. In the Open box, type Regedit.
  3. Locate the following registry key:
  4. Double-Click ConnectionTimeout, and then change the Decimal value to 0.
  5. Click OK, and then quit Registry Editor.
Microsoft has confirmed that this is a problem in Access 2002.

Steps to Reproduce the Behavior

  1. Open any linked Oracle 8i table.
  2. Minimize the table, and then minimize Microsoft Access.
  3. Leave the session of Access inactive for about 1 to 2 hours. Note that after some time, you receive one of the error messages that is mentioned in the "Symptoms" section of this article.
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Article ID: 282349 - Last Review: 12/05/2015 23:19:06 - Revision: 5.0

Microsoft Access 2002 Standard Edition

  • kbnosurvey kbarchive kberrmsg kbtshoot kbbug kbnofix kbstoprespond KB282349