 |
 |
Peter, I believe any client that opens an Access database must have write access to the folder the Db is in so that it can write to the lockfile, [database filename].ldb. This is how Access deals with record locking from multiple users editing it at the same time. So I guess that leaving write access to the folder would be necessary, but that you could apply your permissions to the .mdb file itself (as opposed to the folder it resides in) and achieve your desired result. This should avoid using Access permissions. PS. I haven't actually tested this theory. Cheers, Brian Hoort At 03:25 PM 7/8/2004, you wrote: >Hello > >We have a 5000 record access database that only certain people should >have access to. I've set permissions so that one group of users has >read only access to the database directory, and the other group has >write permissions to the database directory. However, when a user with >read only access to the database directory tries to open the database, >Access reports that it is 'unable to lock file'. I have tried starting >Access with the /ro switch to open a database in read only mode, but >this doesn't work. For some reason, one computer one the network this >arrangement works fine, but none of the others will even open the >database without write access. I realize I could put permissions in the >database itself, but that's not something I want to do. Any ideas?