G
Guest
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
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