Securing the Back-End

[Guest]

I recently secured the front-end of a split database, creating a new
workgroup file. I would like to allow no rights at all for the back-end,
other than for members of the Admins group.

Today I opened the backend file and attempted to reset permissions. Access
told me that I must have Administer rights to do so. I'm a member of the
Admins group in the workgroup file, which has such permissions, so I'm
confused and must be missing something. Can anyone help explain why I'm
unable to change the permissions and what I can do to correct it?

Thank you.

Sprinks

 

[Scott McDaniel]

I recently secured the front-end of a split database, creating a new
workgroup file. I would like to allow no rights at all for the back-end,
other than for members of the Admins group.

Today I opened the backend file and attempted to reset permissions. Access
told me that I must have Administer rights to do so. I'm a member of the
Admins group in the workgroup file, which has such permissions, so I'm
confused and must be missing something. Can anyone help explain why I'm
unable to change the permissions and what I can do to correct it?

When you secured the frontend, did you "join" the workgroup file you created? If so, then you may receive this error
message. Click Tools - Security - Workgroup Administrator and see which workgroup file you're currently joined to. YOu
should be joined to the defaut system.mdw file; if not, find and re-join that file.

You can open your frontend file with your secured workgroup file by building a shortcut with the Target like this:

"full path to msaccess.exe" "full path to your database" /wrkgrp "full path to workgroup file"

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

 

[Joan Wild]

Sounds like you aren't using the correct mdw. How are you opening the
backend?

You could open the frontend and log in as the user you want to own
everything.

Create a new mdb and import everything from the existing backend. You'd do
this because the existing backend is not secured and is owned by 'Admin'
user.

Now go into the security permission dialogs and proceed to secure the new
backend manually - remove all permissions from the Users Group and
double-check the permissions on all the objects.