Article ID: 289681 - View products that this article applies to.
This article was previously published under Q289681
This article applies only to a Microsoft Access database (.accdb and .mdb).
Novice: Requires knowledge of the user interface on single-user computers.
For a Microsoft Access 2000 version of this article, see 202171
For a Microsoft Access 97 version of this article, see 183936
When you try to open a database that is located on a server, you may receive the following error message:
Couldn't use <filename>; file already in use.
If a user opens a database and doesn't have create rights for the folder in which the database is located, the Microsoft Jet database engine can't create the locking information file (*.ldb in Access 2003 and in earlier versions of Access and *.laccdb in Access 2007) that is necessary for multiple users to open the database. Therefore, a user who doesn't have create rights opens the database exclusively if a corresponding .ldb file or .laccdb file does not already exist.
To prevent this behavior, you must make sure that all users who open the database have read, write, and create rights for the folder in which the database is located.
Additionally, if you are using a security-enhanced Access database, you must make sure that the users who open the database also have Read permission and Write permission on the folder that contains the workgroup information (.mdw) file.
In order to open a database in shared mode, the Microsoft Jet database engine must be able to create a locking information file (*.ldb or *.laccdb) in the same folder as the database itself.
For more information about .ldb files, click Microsoft Access Help on the Help menu, type sharing access database in the Office Assistant or the Answer Wizard, and then click Search to view the topic.
For additional information about .ldb files, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/299373/ )Introduction to .ldb files
Article ID: 289681 - Last Review: March 26, 2007 - Revision: 6.1