BUG: Access quits unexpectedly when linked Oracle table is left inactive (282349)
The information in 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: 256986 Description of the Microsoft Windows Registry
SYMPTOMS 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. CAUSE 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.
RESOLUTION To resolve this problem, use one of the following methods. Method 1: Change the ODBC Refresh Interval Setting- Start Microsoft Access.
- On the Tools menu, click Options.
- Click the Advanced tab.
- 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 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. - On the Start Menu, click Run.
- In the Open box, type Regedit.
- Locate the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\ODBC
- Double-Click ConnectionTimeout, and then change the Decimal value to 0.
- Click OK, and then quit Registry Editor.
STATUSMicrosoft has confirmed that this is a problem
in Access 2002.
Modification Type: | Major | Last Reviewed: | 8/10/2004 |
---|
Keywords: | kbstoprespond kbtshoot kbbug kberrmsg kbnofix KB282349 |
---|
|