Secure a Back-End DB in a Split DB

[Tony_VBACoder]

I have split my Access 2002 database into a FrontEnd and
BackEnd database. I have successfully implemented user
security to the FrontEnd Database by the use of a MDW file
and everything works great. I have created an icon which
the user clicks on to launch the database, which has the
full path to the FrontEnd database and the Workgroup file.

I also need to apply security to the BackEnd database,
which has all the tables in it - the FrontEnd database has
all the Forms/Queries/Reports and links to the tables in
the BackEnd database.

What is the best method that I should take to secure my
BackEnd database? I have not found much information in
any FAQ that relates to securing the BackEnd, though I
have found lots talking about securing the FrontEnd.
Also, how will securing both my BackEnd database and
FrontEnd database effect how my users should log into the
FrontEnd database?

 

[Joan Wild]

I also need to apply security to the BackEnd database,
which has all the tables in it - the FrontEnd database has
all the Forms/Queries/Reports and links to the tables in
the BackEnd database.

What is the best method that I should take to secure my
BackEnd database?

Join the workgroup you used to secure the frontend with and open the
backend, and secure it.

Also, how will securing both my BackEnd database and
FrontEnd database effect how my users should log into the
FrontEnd database?

Won't affect it in the least since both use the same mdw file. Just refresh
the links in the frontend.

 

[Tony_VBACoder]

Joan, thank you for all the help. One other question.
With regards to the BackEnd database and trying to prevent
users from opening it with the same MDW file as the
FrontEnd, would you suggest that I remove all permissions
especially the "Open/Run" on the Database object, except
for the "SuperUser" account? This change in permission
should not affect FrontEnd database access, or will it?

Since I am using an icon that the Security Wizard created
to open my secured FrontEnd database that has the path to
the MDW in it, and if someone decided to copy this icon
and change the path of the FrontEnd database to the
BackEnd, the user could potentially log into the BackEnd
database (which is exactly what I am doing to administer
the Users and Permissions of the BackEnd database).

 

[Joan Wild]

Joan, thank you for all the help. One other question.
With regards to the BackEnd database and trying to prevent
users from opening it with the same MDW file as the
FrontEnd, would you suggest that I remove all permissions
especially the "Open/Run" on the Database object, except
for the "SuperUser" account? This change in permission
should not affect FrontEnd database access, or will it?

No you can't do that. Users need to be able to Open/Run the backend
database, but you can remove permission on everything else. In the frontend
use RWOP( run with owner permission) queries for all data interaction.

Since I am using an icon that the Security Wizard created
to open my secured FrontEnd database that has the path to
the MDW in it, and if someone decided to copy this icon
and change the path of the FrontEnd database to the
BackEnd, the user could potentially log into the BackEnd
database (which is exactly what I am doing to administer
the Users and Permissions of the BackEnd database).

But with only Open/Run permission on the database object, they won't get any
further than opening it.