"file in use" error message

[DB88]

John_G: I double checked and I do have "shared" option selected. But maybe another one of my settings is causing a problem. I've attached a screen shot

Z1nkstar: Holding shift and opening doesn't do anything but bypass my "on open" Macro. But all of my tables are linked. More specifically all the tables in the front end are linked tables to the back end. Does that answer your question? Also, I'm willing to call IT and start the process you described, I just want to make sure that I understand what I should be asking them to look for. If there was a locked file, would I see it in the shared folder (aka are you talking about the .accdb file others have mentioned)? Or could only the folder admin see it?

[Z1nkstar]

Well you see I couldn't see it because it was the process that was open and locking the file but are your users opening the separate Front End or off the shared folder?
I am trying to find out how everyone is routed to the back end if they all have front ends then it shouldn't be a problem for each of you to open it with the same back end.

[John_G]

Did you try having multiple users open the backend database directly, rather than going through the front-end? If that works, then there may be a problem in the front-end. What does the macro do? Is it possible that the error is coming from a lock on some other file, and not the back-end database?

John

[DB88]

I split my database and put the backend on the shared drive. Then I gave a copy of the front end to each of my users. They put their own copy of the front end on their local computer. When they open their front end the tables they see are linked tables to the backend. {correct setup}

The only time there is a .lcdbb file in the shared folder is when someone is using the database. There is no orphaned file, the version control file (.lcddb) only exists when someone is in database {working properly}

I've confirmed with IT that everyone has read/write priviledges on the shared drive that is housing the backend {correct setup}

The Advanced Settings on the backend have "shared" enabled { correct setup}

I did the research before I stared building and followed all "sharing" instructions from Microsoft and my reference books. I can't figure out why this is not working. Except for my IT people who tell me that "Access says it can do simulataneous users, but it never really works"

[DB88]

John_G: I just had one of my users open the backend then I attempted to open it as well. I got the error message "Could not lock file". When I clikced ok, it just took me to a blank database. The Macro in the front end just opens the "home" form and locks the navigation pane

[John_G]

The "could not lock file" error is not the one I get when I try to open a database that is already open in exclusive mode - I get the "file already in use error". So I don't think that is the issue.

I'm no expert in this stuff, but it sounds to me as if there is an issue with Access and the .lccdb file. When the second user attempts to open the database, the .lccdb has to be updated, and to do that Access has to briefly lock it. The error message "can not lock file" suggests it cannot lock it, because some other process (the first user) has locked it first - and did not release the lock.

Could there be a setting on your network that when a file is opened, it is also locked; in other words, when a file is opened, is it also locked by default, regardless of what MS Access needs?

It is also possible that the issue lies with MS Access, where it is not properly releasing the lock on that .lccdb file after creating it.

Just some thoughts on where you might look.

John

[ItsMe]

...Could there be a setting on your network that when a file is opened, it is also locked...

@ DB88

What version of server are you using?

[DB88]

John_G: We get "file in use" when multiple users go through front end to get to databse. And "can not lock" when multiple users attempt to enter directly in back end. Your theory about a network setting that locks files sounds reasonable, I will see if IT can look into it.

ItsMe: No idea what server the shared folder is running on. There is a shared drive that my group uses to house our work, at some point (way before my time) it was setup by someone in IT and assigned to us. I have no further information than that.

[ItsMe]

I suppose we can assume this is not a newer version of Windows server.

All we can do is guess that the permissions at the server are OK. You could create a file (maybe a text file) in the share and go around to each user and see if you can open, edit and save the file. But, this may not efficiently eliminate enough variables. I suggest you make a copy of the FE and a copy of the BE and try to replicate the issue on a local machine, like suggest in post #5.
https://www.accessforums.net/access/...tml#post236053

Once you have copies on your local machine, use the link manager to update the links to the table. Now make another copy of your revised FE file. Open both copies of the FE.

[DB88]

I put a copy of backend on my desktop. Then put a copy of front end on desktop and changed the table links to the desktop backend. I then made a copy of this new linked front end and put that on desktop. I can open both front ends and use the database simultaneously. So what does this mean?

[ItsMe]

This means that there is an issue with permissions over the network because you cannot replicate the scenario you just created on the server. I would have probably created folders for the test, but I guess the Desktop will suffice.

[DB88]

So back to my IT people I go. Atleast I know who the folder administrator is this time (That took two weeks to find out last time)

[ItsMe]

Perhaps take your test to the next level and use the Link Manager to update the two FE files on your desktop. Update them to look at the DB on the network.

Another test over the network would be to update an FE on another machine to look at your machine and the BE file on your machine, use a folder somewhere.

Doing this should leave any doubt where the problem lies and you can bring this info of "testing using control groups" to the Administrator.

[DB88]

I just opened my original front end (linked to backend on shared drive). Then I opened a copy of that front end (also linked to backend on shared drive). Both opened and I was able to use database simultaneously. What does that rule out?

[ItsMe]

I would use the link manager on another workstation and try to update to the BE on the server. Then test multiple FE files to the BE on the server.