Sunny said:I am currently using MS 2003 and work on a multi-user database.
I have reviewed previous posts in the forum and followed their advise
achieved in spliting the database to FE and BE, and converting the FE as
MDE file to protect the codes and Forms in the database.
I am proceeding to User Level Security but encountered couples of problem.
Which increased my concerned if it is wised to setup user level security
for the multi FE MDB.
1) I could not could not set User Level Security in an MDE file?? is that
2) I am now sharing the database by deploying FE copies of MDE file to the
other users' PC, is it the same after setting User Level Security MDB??
3) I found that there is a MDW file as well, and another shortcut was
created for logging to the protected MDB, whenever each time I deploy them
as 2) at above, errors comes with not having permission in access to the
MDB, likely due to lost of linking with the MDW file and the MDB file how
to solve that??
Do I really need to modify the properties inside the "short cut for the
secured database" everytime for every users' PC manually??
4) I have tried to use the wizard to create the User Level Security, but
it seems that it had limited the "permissions", I would like to create my
own define permission, how could that be??
It is appreciated if any senior could share their experience in setting up
user level security in MS 2003 as well as if they how they encounter and
fixed the above problems that I have met.
Put your shared MDW in the same location as your shared back end.
Secure your MDB the way you want and the MDE files that you create and give
your users will have the identical settings.
You should only have to create a custom shortcut specifying your MDW file
ONCE for each user and that shortcut should never have to be replaced or
If they do not use your MDW file they should not be able to open your file
at all. If they can then you did security incorrectly.