Security - Am I missing something?

  • Thread starter Thread starter Robcon
  • Start date Start date
R

Robcon

I secured an Access MDB using a new .mdw with account level security. I
created a new Admin password to require logon when opening Access. I created
a new super user and added this user to Admins Group. I removed all rights
from the Users Group. I removed Admin user from the Admins Group.
When running the database on my system the security works as planned.
However if I install the database on a PC that is still joined to the default
System.mdw, no login is required and users can go into the design view of the
database objects.
Have done something wrong? Or is it that easy to break the security?
 
Although someone determined can hack the security, it isn't as easy as
you describe. You have missed a step in securing the mdb. From your
description, I would say that you didn`t create a new mdb while logged
in as the `new super user`, followed by importing all the objects from
the original mdb, then assigning permissions, etc.

Failing to create a new mdb, means that the owner of your mdb is still
`Admin` and that user is common to all mdw files; therefore any mdw will
open the mdb. The owner can do anything, regardless of permissions set
on that username.


Joan Wild
 
Robcon said:
I secured an Access MDB using a new .mdw with account level security. I
created a new Admin password to require logon when opening Access. I
created
a new super user and added this user to Admins Group. I removed all rights
from the Users Group. I removed Admin user from the Admins Group.
When running the database on my system the security works as planned.
However if I install the database on a PC that is still joined to the
default
System.mdw, no login is required and users can go into the design view of
the
database objects.
Have done something wrong? Or is it that easy to break the security?
Click to expand...

Further to Joan's advice, there's a step by step example on my web site that
might help.

Keith.
www.keithwilby.co.uk
 
Thanks, that solved the problem. Once I imported oblects into the new mdb,
the "super user" became the owner replacing Admin user.
 
Back
Top