Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

table security

Status
Not open for further replies.

bronc

Instructor
Aug 28, 2003
145
GB
Hello
I need to be able to enter data into an Access database which is confidential to me only. The rest of the data on the database can be viewed/accesssed/modified by any others. Should that data be placed in a separate table? Should i hide the table? Password?
Thanks in advance.


 
Yes, it should be put in a separate table. You can hide the table, but that's not as secure as you seem to need. I would use Access user-level security and be sure to encrypt the database.

Another possibility is to create a new database on your workstation to hold the separate table, and link that table in the main database. You would be the only person with the new database. If other users attempt to open the linked table they'll get an error message.

Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein
 
bronc

In my opinion, the best way to achieve this task -- guarantee confidentiality of data -- is to create a "back end" database, and place this database in a secure location, and link to the database.

For example, for an HR system, you have salaries. The tblSaleries is created in a separate database, and placed on N:\db\VerySecure - Novell or ActiveDirectory securty restricts access to the network directory. In Access, use either LinkManager or File -> GetExternal -> Link to access the database and the specific table.

Instead of storing the database on the network, you can also save it to your local drive.

By using this approach, you take advantage of the operating system security to restrict access.

Richard
 
i appreciate all solutions. It would be nice if a table were easily, simply, individually pass word protected but i'll try all of your suggestions. Thanks again.
Ed
 
You can setup Access security, specifically using "group" security which will give you "table" security. However, this is a) an all-or-none effort, security will apply to all users who use the database; b) Access security is not as good as network security -- you can do a pretty fair job, especially if you do a lot of internal coding, but there are "loop hooes" such as remote access, linking tables, etc - Access security is not as good as Oracle or MS*SQL security.

...which is why I suggest using network security with a backend database. Using a backend database is a very common apporach within Access.

Richard
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top