Baffled By Security Wizard

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am attempting to secure some currently unsecure databases to an existing
workgroup. After adding a Group that I needed, I joined the workgroup,
opened the first database, and ran the Security Wizard. It seemed to work,
and I verified that the Users group had no permissions and that the Admin
user was not in the Admins group (which I'd done before).

After rejoining my default workgroup, and trying to launch the newly secure
DB from Windows Explorer, expecting to not to get in, I did. I'm obviously
missing something basic about what steps are critical in securing a DB.

Can anyone help?

Also, all the literature I've seen on Security seems poorly written,
focusing on what steps to follow, rather than on the hows and whys. Any
suggestions for any useful references would be appreciated.

Sprinks
 
Also, all the literature I've seen on Security seems poorly written,
focusing on what steps to follow, rather than on the hows and whys. Any
suggestions for any useful references would be appreciated.
Click to expand...

There's a link to the FAQ on my website. If you've read that and are still
baffled, try my step-by-step example.

Regards,
Keith.
www.keithwilby.com
 
Sprinks said:
I am attempting to secure some currently unsecure databases to an
existing workgroup. After adding a Group that I needed, I joined the
workgroup, opened the first database, and ran the Security Wizard.
Click to expand...

If you did it in that order, then it is wrong. You added the Group to
system.mdw, not to your secure mdw. You need to join your secure workgroup,
and then add the group.

You don't have to run the wizard to secure a database. In fact, you will
learn/understand more if you do things manually.
Also, all the literature I've seen on Security seems poorly written,
focusing on what steps to follow, rather than on the hows and whys.
Any suggestions for any useful references would be appreciated.
Click to expand...

The security white paper http://support.microsoft.com/?id=148555
MSDN article
http://msdn.microsoft.com/library/d...s/dnacc2k2/html/odc_AcSecurity.asp?frame=true
Graham Wideman's
http://www.grahamwideman.com/gw/tech/access/accesssec/index.htm (check out
his other references page as well
 
Joan,

Thank you for your response.

I misstated. I did in fact add the Group to my secure workgroup.

I followed Graham's procedure, which was much clearer. For each table to
add, I created a new blank database while logged on to the secure workgroup,
imported all the objects in, and set permissions accordingly. Mission
accomplished. While satisfied that I can continue to do this successfully,
I'm not clear on why importing the objects into a new database was critical.
Is it because I become the "owner" of all objects in the new database?

Sprinks
 
Yes that is an important step. When you import (while logged in as user
'X'), you ensure that user 'X' is the owner of the imported objects.

However, I don't understand why you would do this every time you added a
table. In fact, if you import every time you add a new table, keep in mind
that the permissions don't travel with the table, so you have to reset all
the permissions on your old tables; unless I'm misunderstanding what you
meant.
 
Joan,

I seem to be having my share of senior moments this week. Chalk it up to
Access Security anxiety, my first multi-user launch, high volume in my REAL
job, and lifestyle adjustments related to having two children in college for
the first time.

What I meant was for each *database* to add (to the secure workgroup).

Thank you for your help.
Sprinks
 
Back
Top