L
Larry R Harrison Jr
I have designed an Access 97 database on an NT 4 platform. (Yes, it's
ancient.) I have an issue that I suppose is a long-standing issue covered
before--granting proper Windows security versus Access security.
The problem is that you apparently have to give full read-write WINDOWS
permissions to the folder where the database is located for a user to even
open it, else you get an "already in use" error. Problem is, in doing this,
you leave open the risk that someone could outright delete the files.
Is there any resolution to this--making it where a user can't delete those
files yet they can open the database (AND have full editing permissions also
for other users)? If not, do newer versions of Access have a resolution?
LRH
ancient.) I have an issue that I suppose is a long-standing issue covered
before--granting proper Windows security versus Access security.
The problem is that you apparently have to give full read-write WINDOWS
permissions to the folder where the database is located for a user to even
open it, else you get an "already in use" error. Problem is, in doing this,
you leave open the risk that someone could outright delete the files.
Is there any resolution to this--making it where a user can't delete those
files yet they can open the database (AND have full editing permissions also
for other users)? If not, do newer versions of Access have a resolution?
LRH