How can I hide macros and SQL scripts in Access 2007 without making it a ACCDE file type
Is there a way to hide macros and scripts in access 2007
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"With ACCDE you protect the VBA code,"
Well, a bit more than that. You cannot open modules, forms, reports or macros in Design View.
mx
Well, a bit more than that. You cannot open modules, forms, reports or macros in Design View.
mx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
another way is to distribute your app as runtime.
see this link
http://msdn.microsoft.com/en-us/library/cc136539%28v=office.12%29.aspx
see this link
http://msdn.microsoft.com/en-us/library/cc136539%28v=office.12%29.aspx
Is your concern here at stop a casual user form seeing/running the code/macro?
Or to prevent a company form seeing/stealing your code?
Or to thwart a determined hacker?
...etc
Or to prevent a company form seeing/stealing your code?
Or to thwart a determined hacker?
...etc
Delores_C .. summarizing:
Since User Level Security (ULS) is no longer supported as of A2007, the biggest bang for the buck is to:
1) create a ACCDE
2) Even add a database password.
3) Inhibit the Shift Key bypass as noted by danishani above.
However, note that IF ... a user does open the db, your tables and queries (SQL) are not protected. You can make all of these objects Hidden (a property) ... but of course that can be easily overridden.
Creating a Runtime does very little, because anyone can still take the db onto another system and open it - or even on a system with the Runtime - if that system also has a full install of Office.
So, these are pretty much your options.
mx
Since User Level Security (ULS) is no longer supported as of A2007, the biggest bang for the buck is to:
1) create a ACCDE
2) Even add a database password.
3) Inhibit the Shift Key bypass as noted by danishani above.
However, note that IF ... a user does open the db, your tables and queries (SQL) are not protected. You can make all of these objects Hidden (a property) ... but of course that can be easily overridden.
Creating a Runtime does very little, because anyone can still take the db onto another system and open it - or even on a system with the Runtime - if that system also has a full install of Office.
So, these are pretty much your options.
mx
mx