The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe. SYMPTOMS
When you use older MS-DOS-based database applications with a Windows NT or Small Business Server (SBS) network, you may encounter various errors such as:
RESOLUTION
These older MS-DOS-based database application engines were not developed with the file locking mechanisms that Windows NT enables by default. These settings are used to improve performance of Windows NT-aware applications, but can have different results with applications that do not understand them. The best solution is to upgrade the application to one that is compatible with Windows NT or SBS. If it is not possible to upgrade the application, there are changes in the registry that could improve the performance. These registry entries will turn off the use of opportunistic file locking and the caching of files previously open but now closed, and will prevent the networking portion from closing a workstation session that it thinks has timed out.
MORE INFORMATIONFor additional information about EnableOplocks, please see the following article(s) in the Microsoft Knowledge Base: Q102967 REG: Server Service Entries, PART 1For additional information about CachedOpenLimit, please see the following article(s) in the Microsoft Knowledge Base: Q124916 Some Client Applications Fail When Writing to Windows NTFor additional information about Autodisconnect, please see the following article(s) in the Microsoft Knowledge Base: Q138365 How the Autodisconnect Works in Windows NT Additional query words: smallbiz
Keywords : |
Last Reviewed: March 15, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |