/RO not working with linked tables

[Guest]

I have a database (db1) that uses linked tables in db2. I use a shortcut to
launch db1 with the /ro option. When db1 opens, it announces that it is
Read-Only, but it still allows me to change the data in the linked db2. Any
way to fix this? I'm trying not to use Workgroups. Thanks Bill

 

[rayc via AccessMonster.com]

Bill,

You're working with two distinct database files when you have attached tables.
db1 is read-only but this doesn't automatically make db2 read-only.

When you put /ro in your shortcut, only the file db1 is read-only, but
temporarily....until you close the file.

Nothing stops anyone from double-clicking the db1.mdb file in Windows
Explorer where he/she can modify data.

For a true read-only database, you'll need to implement user-level security.
I'm not sure if this is where you want to go.

Sine you have attached tables, another option would be to write code in db1
that attaches to db2 in a read-only fashion. Or maybe create read-only forms
in db1.

Ray