Make table data read-only to external Access mdbs

  • Thread starter Thread starter CC
  • Start date Start date
C

CC

Data in tables within my Access 2000 database must be editable (read/write)
within the database - using my user interface.

These same tables need to *always* be read-only when others try to link to
them from other Access databases. Is there a simple way to do this?

Thank you.
 
CC said:
Data in tables within my Access 2000 database must be editable
(read/write) within the database - using my user interface.

These same tables need to *always* be read-only when others try to
link to them from other Access databases. Is there a simple way to
do this?

Thank you.

You would use User Level Security. Instead of the normal practice of
removing all permissions to the default Users group you would grant the
group Read-Only access.

Users of your app would use a secure workgroup file and login as a user that
has read/write access to the tables. You would use a shortcut to specify
the secure workgroup as opposed to making the secure workgroup their
default.

Anyone using any other workgroup to link to the tables would get read only
access.

This is neither hack-proof nor "simple" depending on how familiar you are
with user level security, but it's as close as you are likely to get to your
stated goals.
 
Thank you for your thoughtful response Rick.

After I create a login for users of my application that grants read/write
access to the tables in my application -- then, would those same users be
able to link to those tables with read-write access from another Access
database? I don't want them to be able to do that..

:
Users of your app would use a secure workgroup file and login as a user that
has read/write access to the tables. You would use a shortcut to specify
the secure workgroup as opposed to making the secure workgroup their
default.
 
CC said:
Thank you for your thoughtful response Rick.

After I create a login for users of my application that grants
read/write access to the tables in my application -- then, would
those same users be able to link to those tables with read-write
access from another Access database? I don't want them to be able
to do that..

:
Users of your app would use a secure workgroup file and login as a
user that has read/write access to the tables. You would use a
shortcut to specify the secure workgroup as opposed to making the
secure workgroup their default.

If they are in Access while joined to the secured group then yes they would.
However you could remove their edit capability on the tables and bind all
forms used for editing to RWOP (run with owners permissions) queries. They
would be able to do edits via the queries, but would have read only access
to the tables. Since one cannot link to a query this should give you what
you want.
 
Back
Top