stopping the importing of table objects

[mike h]

How do I prevent users from importing table objects from another database.
I am creating mde files that have AllowBypassKey set to false, no menus allowed, an autoexec macro that sets
AllowBypassKey set to false every time the db opens and all the tables are hidden. BUT...... this will not stop a user from writing DAO or ADO code in another MS access database or Visual basic app to identify my hidden tables (for each tbl in tabledefs) and using sql to look at the data.

Does anyone know of a way ..WITHOUT USING ANY ACCESS SECURITY, DATABASE PASSWORD .. TO let user open the database to view the data in forms and reports but stop the user from opening tables directly either from within or from without of the database

 

[TC]

There is no way you will achieve this without emplying user-level security.

MDE files, AllowBypassKey, no menus allowed, and autoexec macros, are
nothibng to do with it.

In an *unsecured* database, all the tables are owned by the default Admin
user. When you start Access against a default workgroup file, you are
automatically logged-on as that Admin user. So, from Access'es viewpoint,
you are now logged-on as the actual owner of the tables in question. And the
owner of a table is always able to import data from it.

To repeat: this is clearly not the answer you want, but: there is no way you
will achieve this without employing user-level security.

HTH,
TC

How do I prevent users from importing table objects from another database.
I am creating mde files that have AllowBypassKey set to false, no menus

allowed, an autoexec macro that sets

AllowBypassKey set to false every time the db opens and all the tables are

hidden. BUT...... this will not stop a user from writing DAO or ADO code in
another MS access database or Visual basic app to identify my hidden tables
(for each tbl in tabledefs) and using sql to look at the data.

Does anyone know of a way ..WITHOUT USING ANY ACCESS SECURITY, DATABASE

PASSWORD .. TO let user open the database to view the data in forms and
reports but stop the user from opening tables directly either from within or
from without of the database