Re: Baffled By Security Wizard

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


.

Relevant Pages

  • Re: Access Security not secure
    ... You should secure it manually. ... > In your test with using a new workgroup and running the> wizard it was in access2000 then again in access2002 ... >>> to work well until I try to access the database on the ... >>>>> I created the Administrator and added him to the> admin ...
    (microsoft.public.access.security)
  • Re: Is someone hacking into our database?
    ... is only about 90-100 mb in size) because the database goes screwy and begins ... but that I know of no way to keep it secure (due to the ... I changed to that workgroup, ... is a member of the Admins Group in system.mdw. ...
    (microsoft.public.access.security)
  • Re: Sticking with a defined Workgroup.
    ... workgroup file called system.mdw. ... So when you 'join' your secure mdw on the server, it is now the default mdw ... My trouble is that when I distributed my secure database by putting ...
    (microsoft.public.access.security)
  • Re: Security - Security & User Accounts
    ... You are currently joined to the workgroup file you secured ... password set so Access silently logs you into the database ... and then how can I set up secure logins for ...
    (microsoft.public.access.formscoding)
  • Re: secure new FE after import
    ... Thanks, Tom. ... were taken to secure the database in the first place. ... that being logged in as the owner and importing all objects from my ... thought the steps that I took would secure it however it didn't. ...
    (microsoft.public.access.security)
Loading