"Sprinks" <Spri***@discussions.microsoft.com> wrote in message
news:61308CFE-93E9-48C2-92EC-7FB0F0E39825@microsoft.com...
>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

"Joan Wild" wrote:

> Sprinks wrote:
> > 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.
>
> 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.
>
> The security white paper http://support.microsoft.com/?id=148555
> MSDN article
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/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
>
> "Joan Wild" wrote:
>
>> Sprinks wrote:
>>> 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.
>>
>> 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.
>>
>> The security white paper http://support.microsoft.com/?id=148555
>> MSDN article
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/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 Wild" wrote:

> 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 Wild
> Microsoft Access MVP
>
> Sprinks wrote:
> > 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
> >
> > "Joan Wild" wrote:
> >
> >> Sprinks wrote:
> >>> 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.
> >>
> >> 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.
> >>
> >> The security white paper http://support.microsoft.com/?id=148555
> >> MSDN article
> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/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
>
>
>