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
LVL 2
CipherISAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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 Access MVP)Database ArchitectCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.