Way to protect against design changes in one mdb?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is there a way to protect against unauthorized design changes in one mdb
without affecting the many other Access databases on the same server ?

(There is currently no Access security implemented at all.)

Thanks,
Tom
 
Joan,
But doesn't user level security affect every Access database on the same
server?
Tom
 
No it doesn't. Security is determined by the workgroup file in use (doesn't
matter what database is open). By default you are joined to the standard
system.mdw that ships with Access.

Every session of Access uses security. It normally logs you in silently as
the Admin user, using system.mdw. Part of implementing security is to
create a new workgroup file. Access often will change your default to this
new mdw. Just use the workgroup administrator to rejoin system.mdw.

It will then use system.mdw for all sessions of Access, unless you override
it. That is best done by creating a desktop shortcut that uses the /wrkgrp
switch to specify a different mdw than the default. So for secure mdb files
you'd create and use a desktop shortcut; the target would look like...
"path to msaccess.exe" "path to secure mdb" /wrkgrp "path to secure mdw"

All other sessions would use system.mdw with no login prompt.
 
This is a common mistake that is often made by people who start with
Access security.

Access security is quite complicated. There is no way you will learn it
by experiment. It is absolutely essential to follow a written list of
explicit instructions, adding & omitting nothing. Try the Access
Security FAQ, often referenced in this newgroup.

If you follow a proper list of instruictions, securing one database
/will not/ affect any other databases on the same machine. If it does,
you haven't followed the instructions properly. If someone tells you
that it /always/ affects the other databases on the same machine, they
don't know what they're on about :-)

HTH,
TC
 
Back
Top