Access security under LAN environment

  • Thread starter Thread starter sid
  • Start date Start date
S

sid

Hi

I have a question which corresponds to the situation
where i have deployed access database in LAN. What i have
done is provided a driectory on the server shared by all
users on the network, and gave them permissions so that
they can access files under that directory but cannot
delet anything. Next, i established links on their
desktop which uses the .mdw file to establish user
permissions and login. I just noticed that users can
directly browse the directory and if they dont have
access to it, they can just open the Direct database
without going through the .mdw file. Can this be
prevented?

Is their an efficient way of doing this so that the users
cannot open the file directly?

thanks in advance
sid
 
sid said:
I have a question which corresponds to the situation
where i have deployed access database in LAN. What i have
done is provided a driectory on the server shared by all
users on the network, and gave them permissions so that
they can access files under that directory but cannot
delet anything.
Click to expand...

That may be OK, but you could run into problems at some point, if users
can't delete the ldb file that gets created in the folder.
Next, i established links on their
desktop which uses the .mdw file to establish user
permissions and login. I just noticed that users can
directly browse the directory and if they dont have
access to it, they can just open the Direct database
without going through the .mdw file. Can this be
prevented?
Click to expand...

If they can do that, then you missed a step in securing the database - they
shouldn't be able to even open the database using their default system.mdw
(which is what they are doing).
Try the steps at www.jmwild.com/AccessSecurity.htm
Is their an efficient way of doing this so that the users
cannot open the file directly?
Click to expand...

Once you have it secured properly, you could hide the folder on the server.
\\server\share$ rather than \\server\share

Also you should split the database and put just the backend on the server.
Give each user a copy of the frontend on their computer.
 
Back
Top