Security: installation level or database level?

[Guest]

I have just been looking at the Security FAQ. Perhaps this is a bit of a
rudimentary question, but, is the security produced by the procedure
described (or by running the Security Wizard) set at a data level (connected
to the mdb file) or at the application installation level (to the
workstation's installation of Access)?

I ask this because, as it is now, our organization stores the database file
on our server (which does not include a local installation of Office) and our
teachers run the database from the server on individual workstation
installations of Office.

If I went through the steps of securing our database on any given client
workstation, would those changes be reflected by other users accessing the
database from other computers in the network?

 

[Douglas J. Steele]

Security is on a file level, done in conjunction with the mdw file.

If you've applied security correctly, then any user trying to access the mdb
would only be able to do so if they have access to the mdw file that was
used when security was applied, and they've been added as a user to that mdw
file.

 

[TC]

If you (incorrectly) use the default workgroup information file,
system.mdw, to establish your security, this will apply at the
workstation level; in the sense that you will /always/ be asked to
log-on, whichever database you open from that workstation.

But if you (correctly) create a new wiorkgroup information file - and
use a shortcut using the /wrkgrp switch to select that workgroup file
when you open your secured database, then, the security is effectiovely
at the database level. Database #1 might be secured (and ask for a
username/password), whereas database #2 might be unsecured (and not ask
for a username/password).

HTH,
TC

 

[Guest]

Thank you for your clarification. I have, in fact, applied the security
correctly on a practice copy of our database. I think I'm actually getting
the hang of this!