Secure a Linked Database

[Guest]

I have an access database on our network, and I want to set another one up
that is linked to the main one, but is read only. I already have the 2nd db
set up, but I need to restrict it to read only. I have tried just making the
file itself read-only, but that only restricts users from saving
changes...they would still be able to add, edit and delete data since that
does not require "saving" which is the only thing restricted when an access
file is read-only. I don't want the users to be able to add/edit/delete data
at all, just view it.

Thanks in advance for any help.

-Denise

 

[Joan Wild]

You can restrict the users to just forms/reports and not allow access to any tables/queries. You can set the properties of our forms to not allow edits,deletes, or additions. Backup your database; you can easily lock yourself out playing around with these features.

Create custom menus/toolbars for use throughout your application.
Create a startup form (a main menu form if you have one) that is opened on startup.
Use the features in Tools, Startup to
set the startup form
set your default menu (the custom one you made)
disable all the checkboxes about allowing built in menus, toolbars, changes etc.
hide the db window (ensure the custom menu you create does not include the Windows, Unhide item)
uncheck the allow special keys (this will disable the F11 key, among others)

If you need to bypass these startup features, you can hold the shift key down while you open the db. If you feel that your users may use this to bypass your settings, you can disable the shift key bypass - there's an example in help for doing this(look for AllowBypassKey) or at
http://www.mvps.org/access/modules/mdl0011.htm
and
http://www.mvps.org/access/general/gen0040.htm

You can also create a MDE from your database, which will prevent changes to forms, reports and modules (If you do this, be certain to keep your original mdb in case you need to make changes).

None of this will keep the determined out. All they need to do is start a new db and link to your's, but this may suffice for your purposes.

Otherwise, you can implement security and set permissions to restrict users.