Access security file off server or C driver

[mar10]

I have a small Access 2000 program than no more than 5 people access at
one time.

I've placed the data on the server and am running the front end off
everyone's C drive with links to the data.

Users open the program with a shortcut that calls the MDW security file
which is also located on the server.

Several times the USER security permissions revert back to allowing
access to everything - I've successfully disallowed this group
access to anything but then will find somehow the permissions return.

Could accessing the MDW file off the server be causing problems?
Should I copy the MDW file down to the individual C drives as well?

Other thoughts as to why this may happen?

Thanks

 

[Rick Brandt]

I have a small Access 2000 program than no more than 5 people access at
one time.

I've placed the data on the server and am running the front end off
everyone's C drive with links to the data.

Users open the program with a shortcut that calls the MDW security file
which is also located on the server.

Several times the USER security permissions revert back to allowing
access to everything - I've successfully disallowed this group
access to anything but then will find somehow the permissions return.

Could accessing the MDW file off the server be causing problems?
Should I copy the MDW file down to the individual C drives as well?

Other thoughts as to why this may happen?

Most likely there are occasions where users are opening the file with some other
MDW file and gaining full access that way. This would indicate that you never
really secured it properly as a different MDW should not allow them to open the
file at all.

The most basic test after applying security is to make sure that you cannot open
the file unless using the proper MDW. If you can then you need to start over.

 

[Albert D.Kallal]

my guess is that the workgroup file is defaulting back to the one on the
local machine.

However, if you, or a ser switches the workgroup file (by intention, or by
accident), and they can get in to the mdb file, then you really don't have
any security at all?

It would be rather funny, and a cruel joke if a user could simply change, or
write over the workgroup file, or even create their own workgroup file, and
then have full use of the file. If you setup security correctly....you loose
the original security file...you will NOT be able to get in.

My bets are that the workgroup file is defaulting back to the local one on
the pc. (or, users are launching ms-access first....and that ignores your
shortcut that includes the workgroup file)....you are using a
shortcut....right? (since, if the server is down..then if users try and
launch ms-access for any old local file, then how will ms-access launch if
you set the default workgroup file to be on the server? (yikes...you better
not do that!!). Further, by setting a default workgroup file..then ALL mdb
files they open will first force the user to logon...and that is also a
unnecessary pain.

It is for this reason you REALLY REALLY want to build a shortcut with the
workgroup file specified. If they try and open the mdb file without using
the shortcut...they should receive a message stating that they don't have
permissions.


It seems right now that changing, or switching the workgroup file allows
users to get in...and that means you HAVE NOT setup security correct. This
means that the file is NOT secured. So, it sounds likely you are using a
workgroup file..but you mdb is not secured...


you need to re-read the security faq.....