“The database has been placed in a state by user…”

Access error 3734. Last updated 17 September 2026.

The database has been placed in a state by user ‘Admin’ on machine ‘XYZ’ that prevents it from being opened or locked.

Usually nobody has done anything wrong. A file that says who is allowed to open the database has been left behind, and Access will not start until it is satisfied about it.

What is actually happening

When somebody opens a shared Access database, Access writes a second file beside it — yourdb.laccdb, or .ldb on older versions. That file is the list of who currently has it open. When the last person closes it properly, Access deletes the file.

So the error means one of a small number of things:

• The lock file was left behind. Somebody’s Access crashed, or their laptop slept, or the network blipped mid-session. Nobody is in the database, but the file that says otherwise is still sitting there.
• Somebody has it open exclusively. Opening in Exclusive mode, or opening a form or module in Design view, takes a lock that shuts everyone else out.
• Permissions on the folder. Access has to be able to CREATE and DELETE the lock file, not just read the database. Read-only rights on the folder produce this error even when the database itself is writable.

The fixes that work

1. Everybody out, then delete the lock file. Confirm nobody has it open, then delete yourdb.laccdb. If it refuses to delete, somebody still has it — that is the file telling the truth.
2. Check folder permissions. Everyone who uses the database needs create/modify/delete on the folder the back end lives in.
3. Split the database if it is not already: tables in a back-end file on the share, a copy of the front end on each person’s own machine. Most of the daily locking pain in Access comes from several people running the same front-end file over a network.
4. Client Settings → Advanced: default open mode Shared, default record locking No Locks.

Those are the real answers and they work. If you are here because it happened once, stop at step one. The rest of this page is for the people it happens to every week.

Why it keeps coming back

None of those fixes changes the underlying arrangement, which is that your database is a file on a shared drive and every person who uses it has that file open across the network. Splitting it reduces how much travels over the wire, and it genuinely helps. It does not remove the lock file, the exclusive opens, or the fact that a dropped connection at the wrong moment leaves a mess behind.

That design was a good one when the alternative was a database server nobody could afford or administer. It is the reason Access put a real database on millions of desks. The cost shows up when three people need it at once, all day, and one of them is at home.

What the other shape looks like

The alternative is that nobody opens a file at all. Each person’s app talks to one authority that keeps the records, and changes arrive as changes rather than as two people writing over the same bytes. There is no lock file because there is no shared file to lock.

That is what Bionic Forms is: a small database where the app and the data are the same thing, running in a browser or as an app on your own machine, syncing rather than sharing. Three people can be in it at once, and one of them can be on a train with no signal.

You describe what you keep records of — customers, quotes, jobs, who is on which job — and it is built around that, with the screens and the links between them. There is no shared drive in the arrangement anywhere.

Where this is honest

• There is no VBA. Automation is a fixed catalogue written as sentences. If your Access application earns its keep through years of tuned code, that logic has nowhere to go here, and we say so at length.
• We are pre-launch. Billing works, the product works, and we are honest about the parts that are not finished. The Windows desktop download is unsigned today.
• The browser is the way in. Nothing to install to find out whether it fits.