A2K Admin in Use

[cvegas]

Using Access 2K and have created and mde file which I put into each users
folder.

If one user is logged in another user will get the "Could not use admin file
in use"
message.

This is on a 2003 SR 2 terminal server and the users are rdp'ing into the
system.

That portion of the server is locked down pretty tight and none of those
users would have any admin rights.

Any direction would be aprreciated.

 

[Arvin Meyer [MVP]]

It may be locked down too tightly. Users need create and delete permissions,
in addition to read and write. Create and delete are needed dor the .LDB
file (locking file) If Access can't lock specific records and tables, it
locks everything.

 

[David W. Fenton]

It may be locked down too tightly. Users need create and delete
permissions, in addition to read and write. Create and delete are
needed dor the .LDB file (locking file) If Access can't lock
specific records and tables, it locks everything.

Delete permission IS NOT REQUIRED. If you remove it, Jet will behave
just like Jet 2.x did, i.e., leaving the LDB file there after Access
closes.

 

[Arvin Meyer [MVP]]

Delete permission IS NOT REQUIRED. If you remove it, Jet will behave
just like Jet 2.x did, i.e., leaving the LDB file there after Access
closes.

And if everyone exits elegantly, all will be fine. Unfortunately, that can't
be counted on 100% of the time, so while Delete permission is not required,
it is still a good idea.

 

[David W. Fenton]

And if everyone exits elegantly, all will be fine. Unfortunately,
that can't be counted on 100% of the time, so while Delete
permission is not required, it is still a good idea.

That all depends. You can put some users in an NTFS security group
that has delete permissions (e.g., administrators) and when they
exit, if there's nobody else in the database, the LDB will be
deleted.

The only benefit to LDB deletion is if the LDB file gets corrupted.
If that's happening, you should probably try to figure out why. It's
usually gots by ungraceful exit from Access, which is itself more of
a problem endangering the integrity of your data than it is by
itself. That is, a corrupted LDB file is a symptom of a problem that
is much more problematic than having invalid entries in your LDB
file.

Undeleted LDB files were not a problem in Jet 2.x (Access 2 and
before), so they really aren't a significant problem in Jet 3.x and
higher.