Preventing import of tables and other objects

[Bill Murphy]

We have an mdb which contains tables with confidential data like salaries.
Although this mdb application is password protected, and salary data is
protected by security logic within the application this does not prevent a
user from creating a new blank database, then importing all the tables and
other objects into it, making them available for viewing.

Is there a way to prevent a user from importing the tables and other objects
into a new database?

Bill

 

[Rick Brandt]

We have an mdb which contains tables with confidential data like
salaries. Although this mdb application is password protected, and
salary data is protected by security logic within the application
this does not prevent a user from creating a new blank database, then
importing all the tables and other objects into it, making them
available for viewing.
Is there a way to prevent a user from importing the tables and other
objects into a new database?

Bill

To prevent access by non-users of the application use your network security and
pace the file in a folder that is only accessible by users of the app.

To prevent accesss by users of the app, the best you can do with an MDB file is
to implement User Level Security (an advanced topic that most people botch).
However; anyone who knows how to use Google could break that if they were
determined to do so.

Bottom line is if you need robust security from users of the app then your data
should be in a server database like SQL Server, not in an MDB file.

 

[Bill Murphy]

Deodev,

I believe you intended to post this as a new post instead of adding it to
this one?

Bill