Securing the back-end.........

  • Thread starter Thread starter Mikey C
  • Start date Start date
M

Mikey C

Hi guys

I'm really banging my head against a brick wall with this one - Please
help!!

I have split my database and managed to secure the front-end exactly
how is needed. However, I'm really having troubles securing the
back-end with the same workgroup. I have managed to lock myself out a
number of times but fortunately I have gained access again.

Can anybody tell me exactly how to do this? My book doesn't go into any
detail about how to actually do it!

Really appreciate it :-)
 
Mikey said:
Hi guys

I'm really banging my head against a brick wall with this one - Please
help!!

I have split my database and managed to secure the front-end exactly
how is needed. However, I'm really having troubles securing the
back-end with the same workgroup. I have managed to lock myself out a
number of times but fortunately I have gained access again.

Can anybody tell me exactly how to do this? My book doesn't go into
any detail about how to actually do it!

Really appreciate it :-)

Open Access using your secured workgroup logging in as an administrator (the
user who you want to be owner of the back end).

Create a new empty file and then import all tables from your current back end.
This is your new back end.

That's it. Just set permissions as desired on the database object and tables.
 
Thanks Rick - sorted now :-)

One more question though ...

Can I restrict access to the back-end of the database, so that only
Admins users can log-in? Not that it makes too much difference but the
files are stored in the same location on the server and i don't want
people to access the back-end.
 
Mikey said:
Thanks Rick - sorted now :-)

One more question though ...

Can I restrict access to the back-end of the database, so that only
Admins users can log-in? Not that it makes too much difference but the
files are stored in the same location on the server and i don't want
people to access the back-end.

All users will need open permissions on the file, but you can restrict
permissions on the tables to admins only and use Run-With-Owners-Permissions
queries in the front end. RWOP queries allow users to access data in tables
that they do not otherwise have permissions to.

With this setup a user could open your back end file, but they wouldn't be
able to do anything else once in there.
 
Back
Top