Error: You Do not have exclusive access....

[trident]

I have a DB used by several staff. We are using the same form simultaneously, If the form is open in another location, and another staff open the same form, this error appears:



YOU DO NOT HAVE EXCLUSIVE ACCESS TO THE DATABASE AT THIS TIME. IF YOU PROCEED TO MAKE CHANGES, YOU MAY NOT BE ABLE TO SAVE THEM LATER.

You have to click the OK button several times just to open the form.

I have made the a BUTTON to Save/Close Form/Open Form to update the counter and record at the same time. So as you can see, every time you save, this error appears.

Can you please enlighten me on this error and how can I overcome this.

Thank you in advance.

Trident

[ranman256]

It usu means someone has the db open.
if you have asked everyone ,and nobody is in it, then try to delete the lock file....ldb, or .laccdb.
if THAT doesn't delete, then everyone must reboot so you can release the lock on the .laccdb file so you can delete it.

then you can edit.

[Bob Fitz]

If you have multiple users then the db should be split so that each user has a copy of the front end on their machine which is linked to a single back end file. The back end file contains just the tables and the front ends usually contain everything else.

[Missinglinq]

From your description I'm pretty sure that Bob has put his finger on the root of your problem! Just to expand on his post, having multiple users sharing a single, non-split database, sitting on a network drive, is the sure way to repeated episodes of corruption, as well as speed and timing problems! Multiple users simply have to work off of a split database, with each user having their own copy of the Front End, which contains everything except the data/tables, on their respective hard drives, and a Back End with only the Tables on a shared drive.

Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past ten years have seen dozens and dozens of reports of non-split apps causing these kind of problems! The really insidious thing is that a non-split app can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!

Here are two tutorials on Splitting a Database:

https://www.fmsinc.com/microsoftacce...abaseSplitter/

http://www.hitechcoach.com/index.php...atid=24:design

Linq ;0)>