If you want to control what users can do, you could implement user level
security. If you go that route, you can deny permissions to modify the
design, and even see some things. It's a steep learning curve, so study up
on it and practice on a copy of your database.
Security FAQ
http://support.microsoft.com/?id=207793
Security Whitepaper
http://support.microsoft.com/?id=148555
Although the whitepaper is old, it contains information to help you
understand security.
I've also outlined the detailed steps at
www.jmwild.com/AccessSecurity.htm
You may find that security isn't necessary, and locking down the interface
and supplying a MDE of your database is sufficient for your purposes...
Create custom menus/toolbars for use throughout your application.
Create a startup form (a main menu form if you have one) that is opened on
startup.
Use the features in Tools, Startup to
set the startup form
set your default menu (the custom one you made)
disable all the checkboxes about allowing built in menus, toolbars,
changes etc.
hide the db window (ensure the custom menu you create does not
include the Windows, Unhide item)
Uncheck the allow special keys (this will disable the F11 key, among
others)
If you need to bypass these startup features, you can hold the shift key
down while you open the db. If you feel that your users may use this to
bypass your settings, you can disable the shift key bypass - there's an
example in help for doing this(look for AllowBypassKey) or at
http://www.mvps.org/access/modules/mdl0011.htm
and
http://www.mvps.org/access/general/gen0040.htm
You can create a MDE from your database, which will prevent changes to
forms, reports and modules (If you do this, be certain to keep your original
mdb in case you need to make changes).
None of this will keep the determined out. All they need to do is start a
new db and link to your's, but this may suffice for your purposes.
