Security wizard: Workstation only security

[NurseHHPMS]

I have created a DB for school nurses (32 Schools) THe DB is not on a
server. It is workstation only. I used the security wizard to set up a
workgroup for passwords and permissions for the DB I created. When I tried
to burn a CD of the DB program for the users on their computers the secuirty
was lost and the program would not open.

Question: Do I need to set up the security wizard on each workstation if
the program is workstation only?

 

[Tom van Stiphout]

On Sat, 12 Apr 2008 18:57:00 -0700, NurseHHPMS

You're so lost bro/sis. Probably because you never downloaded,
studied, and fully understood the Microsoft Security FAQ from
microsoft.com.

-Tom.

 

[QuestionsAcc via AccessMonster.com]

When you say the security was lost do you mean when they try to open the
database they are not prompted for a username and\or password.

 

[Rick Brandt]

I have created a DB for school nurses (32 Schools) THe DB is not on a
server. It is workstation only. I used the security wizard to set
up a workgroup for passwords and permissions for the DB I created.
When I tried to burn a CD of the DB program for the users on their
computers the secuirty was lost and the program would not open.

Question: Do I need to set up the security wizard on each
workstation if the program is workstation only?

Did you include the workgroup file and a shortcut or instructons so that the
workgroup file is used when they try to run the file?

The part of Acesss security that causes you to be prompted to log in is NOT
stored in the MDB file. It is based on what workgroup you are using and
whether that workgroup has a password assigned to the default user "admin".

Without using the correct workgroup a user would be silently logged as
"admin" and if you applied security properly they would be denied access to
the file. It sounds like that part is okay since you say they couldn't get
in.

Your CD should have the MDB, the MDW, and a shortcut example that would be
used to open the file while specifying the secured workgroup. That shortcut
would be in the form...

"path to MSAccess.exe" /wrkgrp "path to MDW" "path to MDB"

The fact that those paths could be different for every user is why you
typically need a real installation program for this rather that just some
files copied to a CD. Users will need to be able to create that shortcut
with the specific paths needed for their situation.

An alternative security setup can be used if all of your "normal users" will
have the same permissions. In that case you can assign those permissions to
the default group "Users" and then they can use your file without your
workgroup file and with no need to log in. They would be logged in as the
default user Admin member of default group Users, but they would still be
restricted to the permissions that you gave to the Users group. Only those
users that need elevated permissions would be required to login with the
correct workgroup file.

If you need all of your users to log in and have various permissions then
this alternative strategy won't work for you.