HELP Security Wizard Questions

  • Thread starter Thread starter Joyce
  • Start date Start date
J

Joyce

I used the secuirty wizard to make 3 levels of user
groups, added the user names and passwords and stored the
database on the network. Now when I as admin log on, it
prompts me for my user name and password, but not the
other users. Anybody else can just access it, they are
not prompted for thier user name and password. I don't
understand why others aren't being prompted for their user
name and password, they have full authority do all tables
and forms but I actually restricted this or so I thought.
Did I do something wrong. Any help you can give me is
appriciated.
 
Joyce said:
I used the secuirty wizard to make 3 levels of user
groups, added the user names and passwords and stored the
database on the network. Now when I as admin log on, it
prompts me for my user name and password, but not the
other users. Anybody else can just access it, they are
not prompted for thier user name and password. I don't
understand why others aren't being prompted for their user
name and password, they have full authority do all tables
and forms but I actually restricted this or so I thought.
Did I do something wrong. Any help you can give me is
appriciated.
Click to expand...

If they are not getting prompted for a login then I would assume that they
are still using their default System.MDW file instead of the MDW file where
you set up your security. The fact that they can use a different MDW file
and still get in means your security setup is wrong. (the wizard blows
basically).

You must first fix your security so that their attempts to get into the
file with the default MDW will fail. At a minimum the following must all
be true.

Default user "Admin" has zero permissions to the database and all objects

Default group "Users" has zero permissions to the database and all objects.

Default user "Admin" is not listed as the owner of the database or any
objects.

The last is I believe where the wizard messes up and is why anyone who logs
in as "Admin" regardless of the MDW file they use will be able to open the
file. Owners have rights irrespective of their assigned permissions or
that of the groups they are members of.

Once you achieve point (1) and users are not able to open the file without
using your MDW then the next step is to create a shortcut for your file
that specifies your MDW file as a command line argument. The syntax for
that is roughly...

"Path to MSAccess.exe" /wrkgrp "Path to your MDW" "Path to the MDB"

This will allow them a means to use your MDW file for your app, while
retaining System.MDW as their default. They could use the Workgroup Admin
tool to make your MDW file their default and then you wouldn't need to
create the shortcut, but this will cause them to "log in" every time they
use Access, even for files other than yours.
 
Back
Top