ACC: "Couldn't Lock File; SHARE.EXE Hasn't Been Loaded" ErrorLast reviewed: May 7, 1997Article ID: Q116387 |
The information in this article applies to:
SYMPTOMSModerate: Requires basic macro, coding, and interoperability skills. When you try to open a Microsoft Access database, you receive the following error message even though you are running SHARE.EXE or VSHARE.386:
Couldn't lock file; SHARE.EXE hasn't been loaded. CAUSEThis error can occur if Microsoft Access cannot perform record locking on the database's corresponding .ldb file. If, for example, the .ldb file is set to Read-Only, either on your local hard disk or on a network server, this problem occurs. With an administrative network setup (setup /a), the .ldb files under the Workdir folder are not created until the first user opens Microsoft Access. This error can also occur if the first user does not have Create rights.
RESOLUTIONSet the .ldb file to Read-Write, not Read-Only. Also give Read, Write, and Create rights to the Workdir folder for each user that is using Microsoft Access.
MORE INFORMATIONMicrosoft Access may automatically create a locking information (.ldb) file for a database. This file will have the same name as the database itself, but will have an .ldb extension and will be created in the same folder as the database. Even if an .ldb file on a network server is set to read-write, network security may cause Microsoft Access to behave as if the file were read- only. To check whether an .ldb file is read-write or read-only, follow these steps: In Windows 95:
REFERENCESFor more information about .ldb files, search for "LDB files" then "Locking Information Files (Common Questions)" using the Microsoft Access Help menu. |
Keywords : EvnOthr kbenv kberrmsg
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |