Another issue

  • Thread starter Thread starter Steph
  • Start date Start date
S

Steph

Thanks for the help I have received on all of my other
issues, everything suggested worked. However,.....

I split the database into FE and BE AFTER implementing
security. Security works great on my FE and .mde file.
However, using the default security.mdw file will let
anyone into the BE.
I received a reply before from a very helpful Eric,
however, I guess I am not clear on how to secure things
with the same .mdw file for the FE and BE. I don't want
to join everyone to the .mdw I created because some of
them work on unrelated databases and need different
permissions there. So I left them joined to the default
file and just put the shortcut to run them through
my .mdw when they are accessing this database.
I have read through the FAQ and it just isn't helping
me understand this issue. I thought since it says in
there that running the wizard will take care of all of
the steps to secure a database, that it would be fine.
Do I still need to follow step 10 and create a whole new
database while logged on as a member of the Admins group?
Sorry for the long post, but I am really frustrated.
Thanks in advance.
 
Hi Steph,
I split the database into FE and BE AFTER implementing
security. Security works great on my FE and .mde file.
However, using the default security.mdw file will let
anyone into the BE.
Click to expand...

That is one of the pitfalls of using the splitter wizard on a secure
database. The backend ends up unsecured. You could have split it manually
and avoided this.
. So I left them joined to the default
file and just put the shortcut to run them through
my .mdw when they are accessing this database.
I have read through the FAQ and it just isn't helping
me understand this issue.
Do I still need to follow step 10 and create a whole new
database while logged on as a member of the Admins group?
Click to expand...

At this point, yes you can. An easy way is to open your frontend mdb and
log in as a member of the Admins group. Create a new database, import the
tables from your existing backend. Go to Tools, Security, Permissions and:

1. Remove all permissions for all objects (including the Database) for the
Users Group.
2. Do the same for the Admin User (there shouldn't be any, but double
check).
3. Assign permissions to the database, and tables for your user groups.
 
Back
Top