A question about securing back end mdbs

[Jesse Aviles]

OK guys. Once we had to implement security at our office and when the
problem finished, security was lifted. Now, we need security once again.
Our mdb is divided in front ends (at each machine) and a back end (at the
server). When I had implemented security before, it was done to the front
end. Now when I thought about doing the same thing it ocurred to me that
the back end (where the data that needs to be protected is) will not be
secured. That any one can take the back end, open it and do whatever they
wanted. I haven't done this but I want to be sure before I mess up with the
back end and maybe leave everyone out of the database (and trying to get my
blood), if I run the security wizard on the back end will it work so that
when an user logs in the log in prompt will show up. If I'm looking at this
in the wrong way, will give some directions to a better solution.
Thanks.

 

[Benn Vosloo]

Honestly I don't know.

What I would do is to make a copy of the database on
another pc and link a frontend to that copy. Then run the
security wisard on the copy of the datebase and see what
happens. This is the way I test all the changes I make to
our database as you well know a small mistake can cost you
a lot of grief.

B

 

[Lynn Trapp]

Get a copy of the Security FAQ (see link below). Basically, after you run
the security wizard on the Frontend, you should not need to run it again for
the Backend. Simply open the backend with the same .mdw file used to secure
the Frontend and modify the permissions as necessary.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Security FAQ: http://support.microsoft.com/support/access/content/secfaq.asp