Securing and Splitting a Database

  • Thread starter Thread starter James Franklin
  • Start date Start date
J

James Franklin

Hi,

Using A2K, I have a database which I want to secure and then split to a
FE/BE solution. I have run the security wizard to secure the database.
However, if I then split the database using the Database Splitter wizard,
the front end is secure, but the back-end can be opened by anyone.

Why does this not remain secure and what is the correct procedure for
securing a split database like this? Do I now separately need to run the
Security Wizard on the backend?

Thanks for any help you can give,
Jim F.
 
James Franklin said:
Hi,

Using A2K, I have a database which I want to secure and then split to a
FE/BE solution. I have run the security wizard to secure the database.
However, if I then split the database using the Database Splitter wizard,
the front end is secure, but the back-end can be opened by anyone.

Why does this not remain secure and what is the correct procedure for
securing a split database like this?
Click to expand...

You can split it manually instead. See
http://www.jmwild.com/SplitSecure.htm
Do I now separately need to run the Security Wizard on the backend?
Click to expand...

If you can, go back to your original mdb (secure but not split) and do it
manually. If you didn't retain a copy of it, then you should open your
frontend, logging in as the user you want to secure the backend with. Then
open the backend and secure it (you'll be securing it using the same
workgroup as the frontend).

However, since you are using Access 2000, the security wizard will leave a
security hole. There are detailed steps at
http://www.jmwild.com/security97.htm you can follow to secure it properly.
 
Back
Top