Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 368
  • Last Modified:

MS Access 2010 Exclusive Access Error when viewing report

I developed an MS Access database (not my choice) and developed some reports for the database.  The database is on the server.  When a second user accesses the same report they receive the below error.  

Sometimes the error pops up multiple times.

Can't figure out why or how to resolve.  Any ideas?
Error.jpg
0
CipherIS
Asked:
CipherIS
2 Solutions
 
macarrillo1Commented:
This can happen a couple of ways:
1. If the user opened MS Access first and navigated to the database they wanted to open. When you open this way you can attempt to open it exclusively.  Notice that the open button has a dropdown (Open, Open Read only, Open Exclusive, Open Exclusive Read Only).  If you open Exclusive no one will be able to open until you exit. In this case you may have to open and close the database to release it.

2. Another situation I have run into is if the database is stored in a directory that does not allow deletes. When you exit Access the lock file is not deleted. Thus MS Access still thinks you are in it.  In this case you need to delete the lock file when you are not in the database and change the permissions to the folder.
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
For starters ... the  basics:
All professional Access applications use a split configuration, with each user having a copy of the Front End on their workstation. Of course, all FEs are 'linked' to the common Back End ... typically on a Server. This is the tried and proven paradigm ... that will minimize issues. Otherwise, all bets are off.

Meanwhile ... if a user opens an Access db, and is doing anything that Access considers a 'design change' ... for example, opening a Form in Design view, or possibly modifying VBA code and numerous other possibilities  .... then you can incur this error message.

And as noted above ... it's always possible the db was opened in Exclusive mode, but ... that is usually not the case.

Regarding the 'lock file' mentioned above, a 'rogue' lock file (ldb, laccdb) is not likely to cause this problem - typically.  But it is true in general that ALL users must have full Read. Write, Modify and Delete permissions on the folder containing the db. Otherwise, it's possible that or a similar error might be rendered, although that particular error does not usually result from this condition per se.

So ... implement the Split configuration first ... and your issue will likely disappear ... especially since each  user will have a separate isolated copy of the FE on their system :-)

mx
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
<please no points>
+1 for what Joe said - and also be SURE to note the "each user having a copy of the Front End on their workstation" part. This is critical to success.
0

Featured Post

Learn Veeam advantages over legacy backup

Every day, more and more legacy backup customers switch to Veeam. Technologies designed for the client-server era cannot restore any IT service running in the hybrid cloud within seconds. Learn top Veeam advantages over legacy backup and get Veeam for the price of your renewal

Tackle projects and never again get stuck behind a technical roadblock.
Join Now