Removed Admin from Admins in my MDW

  • Thread starter Thread starter Mark Page
  • Start date Start date
M

Mark Page

Hi,

I've (under instruction from this news group (Read Joan
Wild and Nick Brandt))created a new MDW to secure a db
that I've built.

I've followed all the instructions to remove Admin from
Admins ie Admin is only a member of users group in my new
MDW.

Admin in my new MDW has no permissions to read designs,
and it works fine in my MDW.

Frustratingly when I join to the system.MDW I find that
although I am logged on as Admin (as I expected with no
login required) the admin user has full permission to do
anything in the db. I have sussed that this is because
Admin is a member of Admins in the system MDW.

I was advised that this would not be so.

The frustration is that I have had it operate successfully
on another PC, but I can't replicate it.

My apologies for this, but can anyone help? There must be
something wrong that I'm doing.

Just in case in my MDW I've checked the permissions for
the admin user.

Thanks

Mark
 
Mark Page said:
Hi,

I've (under instruction from this news group (Read Joan
Wild and Nick Brandt))created a new MDW to secure a db
that I've built.

I've followed all the instructions to remove Admin from
Admins ie Admin is only a member of users group in my new
MDW.

Admin in my new MDW has no permissions to read designs,
and it works fine in my MDW.

Frustratingly when I join to the system.MDW I find that
although I am logged on as Admin (as I expected with no
login required) the admin user has full permission to do
anything in the db. I have sussed that this is because
Admin is a member of Admins in the system MDW.

This would be expected (unless you removed permissions from the Admin user
in the SYSTEM.mdw). You removed permissions from the Admin user in your
custom .mdw file, which is different from the Admin user in you system.mdw
file. If you rejoin your custom file, does the Admin user have permissions?
I would think it would not (assuming you secured your database properly).
Also, unless you explicitly tell Access to open with a particular workgroup
file, it will open using the user/group/permission list of the currently
active workgroup file.
 
When you open an Access file using the default System.MDW, you are doing so as User
"Admin" that is a member of the group "Users".

The group "Admins" is different in every MDW file unless they are created with
identical Workgroup ID numbers. The fact that "Admin" is still a member of the
Admins group in *other* MDW files is irrelevant. If "Admin" has been removed from the
Admins group in the MDW file that was used to create your file then he doesn't get
any of the permissions of the Admins group, period.

If the file will open then one of the following MUST be true.

The user "Admin" has permissions to open the database.
The group "Users" has permissions to open the database.
The user "Admin" is listed as the owner of the database.
 
Back
Top