Making Linked Tables Read Only

  • Thread starter Thread starter Tim
  • Start date Start date
T

Tim

I have a typical MS database with a bunch of user input
forms. For the sake of discussion, we'll call it
the "master database".

The master database has been set up with user-level
security. Some of my users have edit rights in certain
tables.

I want all of my users to interact with the data through
forms. This is good practice, as I understand it.
Furthermore, at the form level I often have code which
does something when a user modifies or enters new data.
Thus, I don't want users to interact directly with tables.

However, I do want to give my users the opportunity to
create custom queries on their data outside of the "master
database" file. Thus, I have recommended that they create
their own personal mdb files and link to the data in
the "master database".

Problem is, when they log into their personal database,
they pass through user-level security, and inherit the
same rights they have when logging into the "master
database". The linked tables will allow them direct edit
access to the tables in the "master database" which is
exactly what I don't want.

Is there any way to set up the "master database" (or the
users personal mdb file) to assure that linked tables in
the personal database are "read only", regardless of their
rights in the "master database".

And, to take this one step further, is there any way I can
protect my data and specify in the "master database" that
nobody can import or link from it, even users who have
write rights within the "master database".

TIA
 
A couple of points:

1. Proper Access design requires that you split your database into two
components -- a backend with all the tables and a frontend with
everything else.

2. Implement security properly on the backend to control what the
users are able to do in the tables. Once this is done properly, it
doesn't matter what program they use to interact with your data --
it's security is always properly managed according to the rules that
you set.

3. You can prevent users from interacting with the tables directly by
using so-called Read With Owners Permission queries, as explained in
the security FAQ.

See the website in my signature for additional information about
security. See Tony Toews site for information about split applications
http://www.granite.ab.ca/accsmstr.htm


I have a typical MS database with a bunch of user input
forms. For the sake of discussion, we'll call it
the "master database".

The master database has been set up with user-level
security. Some of my users have edit rights in certain
tables.

I want all of my users to interact with the data through
forms. This is good practice, as I understand it.
Furthermore, at the form level I often have code which
does something when a user modifies or enters new data.
Thus, I don't want users to interact directly with tables.

However, I do want to give my users the opportunity to
create custom queries on their data outside of the "master
database" file. Thus, I have recommended that they create
their own personal mdb files and link to the data in
the "master database".

Problem is, when they log into their personal database,
they pass through user-level security, and inherit the
same rights they have when logging into the "master
database". The linked tables will allow them direct edit
access to the tables in the "master database" which is
exactly what I don't want.

Is there any way to set up the "master database" (or the
users personal mdb file) to assure that linked tables in
the personal database are "read only", regardless of their
rights in the "master database".

And, to take this one step further, is there any way I can
protect my data and specify in the "master database" that
nobody can import or link from it, even users who have
write rights within the "master database".

TIA
Click to expand...


=======================================================
Jack MacDonald
remove UPPERCASE LETTERS from email address
Vancouver, B.C. Canada
Info about MSAccess user-level security
www.geocities.com/jacksonmacd
 
Back
Top