Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to use Split DB when others are using it 1

Status
Not open for further replies.

JOEYB99

Technical User
Jul 9, 2008
121
CA

I have split a 2010 Access db and users have a FE on their computer's hard-drive (C:) and the BE is stored on a network drive.

Every so often a user will experience the following message when opening their FE,


The Microsoft Access database engine cannot open or write to the file ". It is already opened exclusively by another user or you need permission to view and write its data.


The users have proper network permission to read/write for the BE and their FE database files, as well as for the network folder where the BE resides.


Why is the file name referenced as simply a double quote in the screen message? What else can I check on the database files and network folder for security permissions? Is there anything I can check inside the FE and BE database files that may be causing this error message?
 
Make sure every user has the rights to create and delete files in the folder containing the back-end. Have you looked to see if there is an laccdb or ldb file in the back-end folder when someone gets the error message?

Duane
Hook'D on Access
MS Access MVP
 

Thanks Duane for the quick response.

Yes, all users have the same rights to create/delete files in the network folder where the BE resides.

Yes, I did notice a laccdb file in the same folder where the BE resides. I understand that this is for record-locking purposes. Is this connected to the error message and if so how? Shouldn't another user be able to simply open their FE without receiving the error message?
 
When the back-end is opened or linked to by the first user, the laccdb file is created. If it isn't created, then the first user has exclusive use of the back-end. When the last user exits the back-end, the laccdb should be deleted.

You should try to narrow down who gets the error message and who is using the back-end when this occurs.

Duane
Hook'D on Access
MS Access MVP
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top