We are using Access 97 and I have one user that seems to get an exclusive lock on the DB when they sign on. No one else can use the DB, get the message "DB in use". It is a brand new system and Access installation, so I suspect something didn't get set right in the installation. However, when I go to the Group Permissions for the DB, there is no "Open Exclusive" available. It's not greyed out, it's just not there. That is the case for all the DB's on our entire system. I inherited this situation and while I have ALL authority as administrator, I can't take any chances that might take down the system. Approx. 30 users using various Access DBs every day. My user can sign in from any other PC and not lock up the DB. It's just her new PC that causes the problem. Any suggestions?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Can't get to OPEN EXCLUSIVE prompt
- Thread starter PaulaJ
- Start date
Hi
In Access97, there is a tick box in the open file dialog which allows you open a database exclusively
Another alternative may be connected to Network permissions,
I assume you have the FE on the C: drive and the data on the Network drive?
All users must have full read/write/create/delete permissions in the folder containing the shared mdb file. This is becuase when a user opens the mdb file, Access creates a lock file (.ldb), in the folder containing the mdb, so users must have create and write permission in this folder, similarly when last user closes mdb, the ldb is deleted, so all users must have delete permission in the shared folder.
Hope that helps
Regards
Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now - UK
In Access97, there is a tick box in the open file dialog which allows you open a database exclusively
Another alternative may be connected to Network permissions,
I assume you have the FE on the C: drive and the data on the Network drive?
All users must have full read/write/create/delete permissions in the folder containing the shared mdb file. This is becuase when a user opens the mdb file, Access creates a lock file (.ldb), in the folder containing the mdb, so users must have create and write permission in this folder, similarly when last user closes mdb, the ldb is deleted, so all users must have delete permission in the shared folder.
Hope that helps
Regards
Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now - UK
- Thread starter
- #3
Yes the FE is on C and the DB is on the network. I already checked the Exclusive checkbox on her copy of Access. It is not checked and she always opens it through a shortcut.
She can sign on from any other PC in the network and not lock up the DB. I believe that we did have to assign her "Write" permission on the network level to get her access to the DB in the first place. Prior to that all she got was that she did not have permission, even though I had assigned her all the same permissions as the rest of her group and joined her to the same .mdw everyone else uses. It has to be a default setting on the install of Access and I suspect that we probably don't want her network setting different than everyone else's. But at least that let's her work for now. Thanks for answering, this is really bugging me!
She can sign on from any other PC in the network and not lock up the DB. I believe that we did have to assign her "Write" permission on the network level to get her access to the DB in the first place. Prior to that all she got was that she did not have permission, even though I had assigned her all the same permissions as the rest of her group and joined her to the same .mdw everyone else uses. It has to be a default setting on the install of Access and I suspect that we probably don't want her network setting different than everyone else's. But at least that let's her work for now. Thanks for answering, this is really bugging me!
- Thread starter
- #4
HI
When you say "She can sign of from any other PC in the Network", do you mean when logged in (to the Network) in her name.
What I am trying to establish is, is it a propblem related to a particualr PC, or to a particular (network) user log in Id.
My money is still on a Network permissions problem.
Regards
Regards
Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now - UK
When you say "She can sign of from any other PC in the Network", do you mean when logged in (to the Network) in her name.
What I am trying to establish is, is it a propblem related to a particualr PC, or to a particular (network) user log in Id.
My money is still on a Network permissions problem.
Regards
Regards
Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now - UK
HI
A quick thought, you mention a shortcut, have you checked the actual shortcut on the offending PC? does it have a switch to open db exclusive?
If another user logs into network on the offending PC, and runs the application do they gat same symptom as 'problem' user? Regards
Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now - UK
A quick thought, you mention a shortcut, have you checked the actual shortcut on the offending PC? does it have a switch to open db exclusive?
If another user logs into network on the offending PC, and runs the application do they gat same symptom as 'problem' user? Regards
Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now - UK
- Thread starter
- #7
We recreated her Network signon to be identical to one that worked previously and now everythings peachy. I don't understand what was happening that the .ldb was not created, however. At this point though, I figure if it ain't broke don't fix it. But it would be nice to understand for the next time. Thanks for answering.
I had a similar problem with my PC. If I signed onto the computer it wouldn't let me run my Autokeys macro, but if another person signed onto the same computer they could. Turned out to be a corrupted Profile. They recreated my profile and everything works great. Might be the same issue as having a corrupt profile on that computer.
Ellie
**Using Access 97 at work**
**Using Access 2000 at home**
lena.wood@starband.net
Ellie
**Using Access 97 at work**
**Using Access 2000 at home**
lena.wood@starband.net
- Status
Similar threads
- Locked
- Question
- Locked
- Question
