Jarda said:
Hi, I need to secure database divided to back-end (data) and
front-end (user interface), using the same workgroup file (which I
have to create yet). I know, how to secure one database contained in
one file, but don't know how to secure divided database.
How to secure both back-end and front-end with one workgroup file? Is
it possible or not?
Thanks in advance for any suggestions
Every file you have opened to this point has been while using a single mdw
file (the default System.mdw). That should illustrate that any number of
files can be opened while using any particular mdw file.
If the mdw file being used requires you to log in (because it has a password
on the Admin user) then you will be required to log in any time you use that
mdw regardless of which file you might open.
A secure file is nothing more than one which expects *certain* login
credentials and typically NOT the user "Admin".
Any file you create while logged into a particular mdw file will be owned by
the user that you have logged in as. If you then remove all permissions to
"Admin" and the group "Users" in that MDB you now have a secured file (to
the extent that Access security can be called "secure"). Using that method
you can create as many secured files as you like that can be accessed with
that mdw file.
Rememebr that mdbs and mdws are not "linked" in any way. There is a
correlation only. A secured MDB expects certain user accounts and/or group
memberships to allow access to the file and the objects within. An mdw file
contains user accounts. Any mdw that happens to contain user accounts that
"satisfy" the mdb will let you into that file. It just so happens that with
an unsecured file ALL mdws satisfy that criteria and with a secured file
only certain mdw files do (usually exactly one).