Securing the tables

[Ryker7]

Is there a way to block users from looking or altering the underlying tables? I have some users that stumbled upon the tables and are now in a position to alter data.

 

[mph1]

I can appreciate that the problem you are encountering is quite perplexing. There are several ways to solve the problem.

1. convert the database, which is an .mdb into a .mde.
2. highlight the table, right click and go to properties, then make the attributes Hidden.



HTH

An investment in knowledge always pays the best dividends.
by Benjamin Franklin
Autonumber Description - FAQ702-5106

 

[Ryker7]

First, what is the difference between MDB and MDE?

Also, I highlighted the table and went to properties, but did not see anything about attributes. What did I do wrong?

 

[willir]

Ryker7

...Picard here...

The MDE is a self-contained executable where the forms, reports have been compiled. The data objects can not be viewed in design view, and coding can not be reviewed either. This does a great job of securing the front end.

But this is just for the front end. (See posts and read up on front end / back end or splitting up the database).

To hide the tables, right click on a table, select properties. You will see "Hidden" check box under the attributes at the bottom of the window / form. Unfortunately, the more experienced end users will know this trick.

You can also setup user and group level security.

 

[worldatlas]

If I use the attributes and hidden all my tables, can this process be reversed where my tables are visible again?

 

[PHV]

menu Tools -> Options ...
tick the checkbox Hidden objects on the 1st tab

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[MichaelRed]

Hiding" the tables is -at best- a minimalist approach. Anyone with even a modest user background can easily 'devine' that they (tables and / or other obkects) are hidden and find the setting to be able to see htem, hten reverse the hidden attribute.

If you have users who have wended through the process of getting to the db window, only concentrated effort will, htereafter, keep them at bay.

I would advise splitting the db, using MS Access security to require user level password to BOTH FE and BE, accessing the tables only through the (UserName/Password) opening of the BE and then making the FE into an MDE.

Of course, this is a bit of work (sixteen tons?), but keeps the entire operation in your control.





MichaelRed

 

[PHV]

The companion of secured tables is WITH OWNERACCESS in the queries.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886