Front end, Back end, and restrictions on which Forms can open.

  • Thread starter Thread starter mpfohl
  • Start date Start date
M

mpfohl

I've created a Microsoft Database that will be split front end and back
end to be shared over the network but i'm having trouble with how to
secure it all. The Backend will be on a shared drive, the front end
will be on individual computers as an MDE.

1) I've used the security wizard but that only secures the front end.
Do i just run the same wizard to secure the back end?

2) I have one form that I would like to restrict access to (it is for
administrative functions on the database). Is there a way to set
permissions to that specific form so that the Administrator can open it
but the average user cannot?

Thanks for any help out there
 
1) I've used the security wizard but that only secures the front end.
Do i just run the same wizard to secure the back end?
Click to expand...

No. I would open the frontend using the desktop shortcut the wizard created
for you - this'll ensure you are using the same workgroup as you used to
secure the FE. Now hit Ctrl-O and open the backend. Now you can run the
wizard - choose to modify the existing workgroup file, rather than creating
a new one. This will secure the BE and it will also create a desktop
shortcut to the backend - delete this shortcut. Now open the FE again and
refresh the links to the new secure backend mdb.
2) I have one form that I would like to restrict access to (it is for
administrative functions on the database). Is there a way to set
permissions to that specific form so that the Administrator can open
it but the average user cannot?
Click to expand...

I assume you have some Group that 'Administrators' belong to. Grant open
permission on this form to this group and deny permission to all other
groups. If this form has a recordsource, then the Administrators will also
need at minimum Read Data permission on this table/query.
 
It isn't working.

I do the Ctrl+O after securing the front end and secure teh back end
using the same method and selecting the same security file. It says it
is secured but when I double click on the file, it still opens without
asking for user name and psw. what am I missing?

And do I need to secure the FE at all if it is an MDE file?
 
If you are able to open it, then the Users Group still has permissions, or
the Admin User still owns the database. Are you sure you are opening the
right mdb?

Try this:

Open the FE, logging in as a user that will own the backend. Create a new
mdb and import all the objects from the backend. Go to Tools, Security,
Permissions
- remove all permissions for every object for the Users Group.
-grant whatever permissions are necessary for the groups you have created
(don't forget the database object).
 
I specifically followed your first directions several times, each term
ensuring that 'users' were granted no permissions (as i did when i was
securing the front end) and it still lets me open it. Then when I go
back to assing permissions, none of the user levels i created using the
wizard 'stuck'. it only has 'admin' and 'user'. very very odd. am i
missing a step?
 
I'm thinking that it isn't usng the correct mdw during the wizard. Try
setting the security manually as described below
 
doing it by hand did it. Thanks again.


Joan said:
I'm thinking that it isn't usng the correct mdw during the wizard. Try
setting the security manually as described below
Click to expand...
 
Back
Top