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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Secure Access tables from being imported from another 1

Status
Not open for further replies.

Duncanmcl

Programmer
Dec 23, 2000
61
US
I have created an semi-secure Access application using front end PW,plus a 2nd PW on modules, and restricted the properties windows to be 'design view only', set view properties on startup to off (menues,short cut keys/menu and I control 'allowbypasskey' via VBA. It is menu driven only, no tables, queries, forms, reports or menue's are visible normally to the user. Users are given the application PW to open. They also have a PW on their account to open their data.

The issue is from another Access DB where they can import from this DB.(after being prompted for the front end PW) ..see the tables, queries, forms etc since they may know the front end PW. Is there a way, similar to the way modules which have this 2nd layer PW which the users won't know and therefore the code remains protected, but not the tables?

Please advise

Thanks in advance...Jim
 
One thing you can do is change all the queries and tables to hidden. Then, unless they think to change their options to display hidden tables, they won't see the tables to import.

Also, check out the forum for access consultants and developers. There is a thread there called "working with Power users" in which I asked similar questions to you. They gave me a ton of great advice!
 
Jim,

You're protecting what is (arguably) the least important part of your system (the code) and leaving the most important (the data) completely unprotected. Not only can anyone who has the password import data into a new MDB file they can also link tables and make unvalidated entries direct into your live tables.

In my opinion something can't be semi-secure - either it is, or it isn't. The best you can hope for with MS Access is making it as secure as possible I would *strongly* recommend you apply full user-level security to your database. Although this is also easy enough to crack with readily available applications it's about as secure as you're going to get with MS Access.

Ed Metcalfe.

Please do not feed the trolls.....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top