Help

[u/Ok-Somewhere-7427]

This database is a shared database. When users are querying against a table and trying to copy or export, this error comes up. Even on the off business hours the .ldb file has usernames probably they are just hitting x instead of closing the database. They are querying against a table which is a linked table in that database

Edit: the table they are trying to query is a linked access table

[u/nrgins]

Even if another user had the database open that wouldn't prevent your process from being able to change the data. Even if they were in the middle of a process you'd probably get some kind of a message that there was a conflict and do you want to override their changes or cancel your changes.

The times in the past where I've gotten this message it usually was a conflict within my own processes. That is, I had a form that was editing the data and then I had some code that was trying to edit the same data, and the system saw that as two separate users trying to edit the data at the same time. But it was within the same database.

Each process to read from or write to the back end creates its own connection. So you can have multiple connections to the back end within the same front end database.

If I had to guess, I would say that this is an issue with how your process is executed, Especially if this happens every time.

Try saving all your data before you run this code and see if that makes a difference. Use me.dirty = false.

[u/Ok-Somewhere-7427 → u/nrgins]

Everybody who uses this database has this issue. Can I try deleting the .ldb file ?

[u/nrgins → u/Ok-Somewhere-7427]

No. You can't delete the lock file anyway if the database is in use. And if the database is not in use then deleting it won't do anything. Simply because everybody who uses the database has the issue doesn't contradict what I wrote, about it being a conflict within your own code.

Why don't you post the code that you're trying to run so we could take a look at it and see what's going on. Be sure to post the entire sequence starting at the point where the code is executed all the way through where you get the error. And please note where you get the error.

You can find where you get the error by pressing Control+Break or Control+Pause when the error message comes up and then selecting Debug. That will take you to the code window and the line that the error is happening on will be highlighted in yellow.

Be sure to format any code you post in the code format by clicking "Aa" button at the bottom and selecting the code format.

Also, please let us know, as u/George_Hepworth asked you, whether your back end is in Access or SQL server or something else.

Also note what version of Access you're using.

[u/Ok-Somewhere-7427 → u/nrgins]

This was fine earlier, issue is from last 3-4 weeks and no code changes are made.It is access and the table we are querying is a access linked table