Users Locked out on Split FE/BE DB

[Ruth]

I have a database that is split between a front and back end. The BE is on a shared network directory. Each user has a copy of the FE on the local (C: ) drive of their computers.

Users only have access to viewing pre-programmed reports. They are not changing objects. Some users are getting locked out when they try to login and another user already has the DB open. This only happens with some users (of course it's never happened to me - the developer). I have a very simple setup. I'm not using MS Access security. The BE is password protected. My users have no interest in Access beyond using the form buttons to see their reports.

Some users are on XP, others on Win7. Any ideas why some get a lockout if they're not able to get exclusive access on the BE?

Thanks, Ruth

 

[SOS]

Do each of the users have READ/WRITE/DELETE rights on the server folder where the backend resides? If not then Access may not be able to let them in.

 

[Ruth]

They can get in to the server if no one else has the DB application open. So I believe it's a sharing issue, not a rights issue. Agree?

 

[SOS]

It still could be a rights issue. Verify for sure that they have the correct permissions.

Also, you didn't change any of the default record locking settings when you developed this, did you? The default record locking should be set to NONE and then Open using record level locking checkbox checked.

 

[DCrake]

Also other things to try is....

1. Log into a machine yourself (one that is causing problems for a specific user) and load the db. Do is still error?
2. Get a user who is experiencing problems log into your machine and open the db. Does it error?

If the answer is Yes to either one then it could be a problem with the users profile.

 

[Ruth]

Yes, turns out it's a rights issue. IT is being mildly helpful. I'll see if it works...

 

[barlee]

Ruth, can you tell me what kind of rights issue it turned out to be? I am having a similar problem. 'Everyone' has full rights to the network folder that the db is in, but only one user can open the db at a time. The second user doesn't get an error, doesn't get a dialog saying the file is locked, it just won't open......

 

[Ruth]

Mine, it turns out, was easy. I thought that all of my users had full rights to the directory. Turns out that the ones with problems had "read only" access. IT set up a new subdirectory for me that supposedly everyone has full access to, but I haven't done the work to move everything over yet and test. I was also disappointed that they're only letting us use a subdirectory, meaning that my BE will be yet a level deeper in the network. I'll let you know how it works.