Securing Back-End, Using one .mdw file on FE & BE

  • Thread starter Thread starter saip15
  • Start date Start date
S

saip15

Hi everyone,

I can't seem to figure this problem out. I currently have a split DB with
ULS and the FE security works great. I am using a shortcut to open the FE, I
have gone through all appropriate steps to properly secure the DB.

I wanted to add some security to the BE so at first I just added a DB
password which I know doesn't do much but at least the novice user can't
access the data. This work fine but then i ran into some problems with a few
of my codes passing the DB password. So I tried creating a shortcut for the
BE using the same .mdw file from the FE. I am using a shortcut creator so I
know that the shortcuts work fine.

For some reason when I create the shortcut for the BE it works fine when I
use the shortcut. But the BE can still be opened directly and no security is
applied. The Admin rights have been disabled completely and in correct way
for the .mdw. I have tried logging into the .mdw and then opening a blank
database and importing the tables in and when I do that the owner becomes
"unknown" when opening the DB directly. Thanks for help!
 
Ok, so I figured it out. When I would open the BE using the shortcut it would
override my permissions and give the Users group all the permissions because
the owner was still Admin. So I opened the BE using my .mdw and created a new
database as the owner and imported the tables. After that I reset the
permissions and everything works fine now and the database can't be opened
directly.
 
It sounds as though the Users Group still has Open permission on the
Database Object - double check that. If you secure it properly, then
you shouldn't be able to even open the mdb using the standard system.mdw

Sounds like you are following the right steps..
You open a session of Access using your secure mdw and logging in as the
user you want to be owner.
Create a new mdb, and import all the objects from your original BE file.
Remove permissions for every object for the Users Group
Apply permissions, if any, to your Groups.

Joan Wild
MS Access MVP
 
Yup, Thanks Joan for all of your help!

Joan Wild said:
It sounds as though the Users Group still has Open permission on the
Database Object - double check that. If you secure it properly, then
you shouldn't be able to even open the mdb using the standard system.mdw

Sounds like you are following the right steps..
You open a session of Access using your secure mdw and logging in as the
user you want to be owner.
Create a new mdb, and import all the objects from your original BE file.
Remove permissions for every object for the Users Group
Apply permissions, if any, to your Groups.

Joan Wild
MS Access MVP
Click to expand...
 
Back
Top