Discussion Locked

Read Only Access to Shared .MDB file.

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have 5 users that need full access and 5 users who need read only access to the database. If I apply full rights to the .ldb file to the read-only users everyone can access the database the way they should. But when the database is closed at the end of the day, the .ldb file disappears. So do the rights to the file. The next time the read-only users attempt to login they receive an "already opened by ...." message. How can I work around this, or save the .ldb file?

9 replies

by bchesmer

If this is a MS-Access database. I would recommend going with the security features built in to access. If u need more info from me or wish to send me more detailed info feel free to contact me via email.

by suvefx

I don't want any security at the hands of the user. This should all be administered from the NDS.

by acurrin

The LDB file is only there to maintain proper database locking during use. If you give full rights to the folder, but read-only rights to the MDB file, Access should be able to create and modify the locking files, while leaving the DB alone.

Good luck

by rogerndgreen

I have had a similar poroblem at work, and unfortunately in my case, providing only RF rights meant that the users could not open the database (Access required the "traditional" RWCEMF before it stopped complaining). In this case, I had to go down the route which you have already rejected in the first answer, and use Access's built-in security to provide the different level of protection. It's not ideal.
Depending on how "real-time" you want the read-only users to be, you could create a copyof the actual DB, give them the rights they need (if they modify it, it's their fault) and then use toolbox & cron to schedule a regular job to overwrite this copy with the "live" one.
HTH

Roger

by isys

What I did: Make two groups-one with RF and one with RWCEMF rights. Apply these to the folder (directory) where the files reside. That way whatever happens to the contents, the IRF maintains your security. The read-only people will get a notification that the file is read-only when they open it. I also have a short-cut to the file on their desktop to make it easier for them to open it.

This discussion is closed to new replies.