User Level Security

  • Thread starter Thread starter Chris Connolly
  • Start date Start date
C

Chris Connolly

Question: One of the users of our Access 2000 network
database is no longer being prompted to enter her
password. Instead the database just opens for her without
password prompting. This appears to be specific to her
computer as other computers in the lab prompt for
passwords and will accept her password. Any ideas?

Much appreciated - Chris
 
Chris Connolly said:
Question: One of the users of our Access 2000 network
database is no longer being prompted to enter her
password. Instead the database just opens for her without
password prompting. This appears to be specific to her
computer as other computers in the lab prompt for
passwords and will accept her password. Any ideas?

Access only prompts for a password when the user is running Access with a
workgroup file (mdw) that has a password applied to the default user
"Admin". Normally when you secure an Access app you do so by creating it
with a workgroup file that has a password applied to the admin user (you
obviously did this). However; the user can change the mdw file that they
are using at any time. They can specify a different mdw file as a
command-line argument when opening Access and/or they can use the workgroup
administrator utility to change the default mdw file that Access will use.
The user that is not getting prompted likely has a different mdw file as
her default and the one she is using does not have a password applied to
the Admin user (so she is not prompted).

Here's the kicker. If she can use another mdw file to open your
application, then you didn't apply security properly in the first place.
When whatever happened to cause her to switch MDW files occurred, she
should have found that she could not open the file at all. She should
receive an error message along the lines of..."You don't have appropriate
permissions to open this database...".

So you need to do two things. You need to correct the problem that allows
her in with an different mdw file. After that is fixed you need to either
change her default mdw file to the correct one or build a shortcut for her
that specifies the correct mdw file as an argument. The latter is the
preferred method. That way the user is not bothered with logging in except
when they use your secured file.

Chances are one or more of the following is incorrect in your security
setup.

The default user "Admin" still has some permissions to the db (should have
none).

The default group "Users" still has some permissions to the db (should have
none).

The default user "Admin" is still listed as the owner of the db (should not
be).
 
Question: One of the users of our Access 2000 network
database is no longer being prompted to enter her
password. Instead the database just opens for her without
password prompting. This appears to be specific to her
computer as other computers in the lab prompt for
passwords and will accept her password. Any ideas?

I don't know how "savvy" this user is (the F1 key can empower the average user),
but, in addition to the suggestions offered by Rick, check to see that this
user's shortcut doesn't have the "Username" and "Password" switches included in
the "command-line". These switches look like this (and is in addition to the
/wrkgrp switch) and can pass the username and password to Access eliminating the
login dialog:

/user MyUsername /pwd MyPassword

:-)
 
Rick,
After reading your reply I checked the priveliges for
admin in a database I had created using the security
wizard. Although I'm not having any problems (yet) the
database seems to have been created with both database
permissions and ownership for the admin. Does anyone
know how this might have happened and tell me why this
becomes a problem for people if the wizard sets it up
this way? Gabe
 
Gabe said:
Rick,
After reading your reply I checked the priveliges for
admin in a database I had created using the security
wizard. Although I'm not having any problems (yet) the
database seems to have been created with both database
permissions and ownership for the admin. Does anyone
know how this might have happened and tell me why this
becomes a problem for people if the wizard sets it up
this way? Gabe

I've never used it, but from what I've read the wizard never produces a properly
secured app.
 
Back
Top