Security For Non-Network Situation

[JKB]

I have a split front-end back-end application that I have completed for the use of 2 other employees who share a single PC. Unfortunately, we are not on a network at this time, so I will have to make a copy of the "master application" on my PC and put it on the PC for the other employees must use. The table data rarely changes, and the application is mainly for use for looking up information and making calculations based on existing data in the tables. Some of the information is personnel in nature (pay rates, etc.) and is not appropriate to these staff members. They are computer savy. In trying to secure this information, I am concerned about the following:


Even linked tables can still be viewed.
Opening the back-end can permit modifications to tables.
A database could be copied to diskette and taken off site for "exploration".
Table based passwords could be viewed or otherwise "gotten around".


Is there a way to secure an application from such possibilities? Does the Administrator/Workgroup setup (which I have not studied extensively) help? Will making the application MDE help? Can individual records in tables be made "not visible"?

What is one to do to secure information when only one PC is available for several people to use?

 

[pcs]

your concerns are valid and well thought-out. i can't really see that a network is the solution though. i think the problem may stem from making available the data from a "master application". without seeing your design, i am guessing that you are providing a front-end for these users that has a back-end with data that has security implications.

would it be possible to change the back-end for these users to a sub-set of the "master application"? you would need to provide code to periodically update this sub-set, but the security would be enhanced.
then, you could use the Administrator/Workgroup settings to secure the "master app". access security is a bit lacking in any case, and computer-savy users are always a threat.

hth

al

 

[ElsVanMiert]

The solution of your problem is in activating the security system on both backend and frontend and using queries with OwnerAccess Option activated.
Feel free to e-mail me if you need more details.