Peter Thesiger said:
Is there any way to (re)connect a d/b to its .mdw file?
There are 2 databases that use the same .mdw for security
purposes and they have become disconnected so users are
able to logon without any security (unless they
are "joined" to the actual security .mdw).
You have a misconception of how Access security works. It is not "per-file" but
rather "per-session".
You first open Access with a specific mdw file. That mdw file is either
specified in the command line or the user's default mdw file is used. If the
mdw file that is used has a password applied to the "Admin" user then you are
prompted for a UserName and Password, otherwise you are logged in automatically
as the "Admin" user (unless a different UserName was specified in the command
line). The mdw file also specifies which groups that particular account is a
member of.
Once the session has been started and a UserName has been established, the file
being opened then "decides" if that user or any of the groups he is a member of
has permission to open the database. If not, then the file is not opened and an
error is displayed.
The reason it *appears* that a file is attached to a particular mdw file is that
one normally creates custom users and groups when securing a file and only
allows those custom users and groups to open the database. Thus the file cannot
be opened unless an mdw file is used that contains these custom users and
groups. If users can open your file with any mdw file other than the one used
to secure it then the file is not secured properly.
Most likely the default user "Admin" and/or the default group "Users" still have
permissions or ownership that they should not have. Once that is corrected then
you should find that users *have* to use the correct mdw file or they won't be
able to open the file.
