Re: Copy secured database to include security

Tech-Archive recommends: Speed Up your PC by fixing your registry

"OssieMac" wrote:

Thanks to both Chris and Keith. I'll try again.

You're welcome! Always glad to be of help, especially since I've received
so much help here!

I had done this "You want to remove Admin from the Admins group." and the
following I also understood:
"P.S. Do NOT assign permissions to users... it makes things too
complicated. Rather, assign permissions to groups and then assign users to
groups. MUCH easier!"

Good! That's a start.

What I didn't properly understand was about creating a another user group
and removing the permissions from the default Users group. I did create the
new user group but did not remove the permissions from the default Users
group.

The problem with leaving permissions assigned to the default Users group is
that anyone with Access can then use a generic workgroup file (i.e. the one
that comes with Access) to gain entry to your database. By remmoving the
permissions from the Users group and assigning them instead to a custom group
you have created, you thwart that entry point.

I can see how this should work now and should overcome my problem of
not being able to remove the Admin user from the users group.

You can't delete the Admin user, nor can you remove Admin from the Users
group... Access insists on having things this way. As well, you cannot
delete the "Admins" and "Users" groups... they're required, too. So, what
you want to do is make sure that the "Admin" user doesn't belong to the
"Admins" group and the "Users" group doesn't have any permissions. Having
either (or both) of those leaves your database wide open to intruders.

Will see how I go with the next attempt and pleased to know that I am not
the only one "Who went through similar agony ."

LOL! I think we *all* have gone through that agony at one time or another.
Frankly, user level secruity is *not* a trivial subject and one wrong move
can negate everything you're trying to do. IMHO, Microsoft didn't make it
any easier by having a default "Admin" user plus an "Admins" group.... it
makes things quite confusing if you're new to all this. Thankfully, this
forum (and others) are available to help us figure it all out.

Btw, I'm learning that getting user level security right is NOT a one-shot
deal. I find that I'll set things up, do some testing or development, and
quickly find that things aren't quite how I want them so I'll make changes.
In the application I'm currently working on, I think I've gone over the
security setup three times now. It's getting closer to what I want, but I'm
sure there'll still be changes as I continue working on it.

So, don't dispair! Read the FAQ, ask questions here, and (eventually)
you'll get it where you want it.

Anyway thanks again for the help. Much appreciated.

Again, you're welcome! Btw, one last comment... As in real life, where if
someone is determined to break into your house they'll probably succeed, user
level security in Access may prevent casual attempts at compromising your
data but someone who's determined to get in probably will get in. So, if
you're data is *really* sensitive, you're better of going to SQL or something
else that's more secure than Access.

Good luck with your quest....

Regards, Chris

.

Relevant Pages

  • Re: would it be wise???
    ... There are some permissions that are necessary by all users, ... The Admin user is only a member of the users group. ... If the user logs in with username and password from the correct ...
    (microsoft.public.access.security)
  • Re: Access 2003 - Security
    ... set up in the users group can get into the database without any ... has permission on the Database object (this group should have absolutely no ... permissions to anything). ... Or perhaps the Admin User still owns the Database ...
    (microsoft.public.access.security)
  • Re: would it be wise???
    ... ...."Some permissions I allowed to the users group, because they are necessary for all ... This includes zero permissions on the Database ... By giving any permissions to the Admin User or the Users Group, ...
    (microsoft.public.access.security)
  • Re: Users Group and User Permissions
    ... You need to ensure that the Users Group has NO permissions. ... you did not delete the Admin user - that is impossible. ... Do they need any permissions for the query itself? ...
    (microsoft.public.access.security)
  • Re: security only works on my PC
    ... I checked the permissions box and the Users group has no ... Open/Run and open exclusive on database object ... Open it using your shortcut and log in. ... Click on the Groups option and select the Users Group. ...
    (microsoft.public.access.security)