Yes, you can use the settings in the tools->start-up.
Generally, once you reach the point of deployment, you do the following:
-- split the database into a front end, and back end (this allows you to
update code for the target pc, but NOT touch the uses current data file).
This solves the problem of you upgrading your application. How did you plan
to do that now?
-- Distribute a mde. This means that your application is free of compile
errors (you compile lots...right?), and further the code, and forms and
reports CAN NOT be modified in a mde (this includes you also...so don't
loose the original mdb file!). This approach allow compete control of your
original design...and it is not possible for your users/clients to change
it.
-- Hide all of the database windows, and turn off a lot of the special
ms-access keys. All this stuff can be done in the tools->start-up options.
And, you might even further disable the shift key by-pass at start-up.
If you want to see an example program with all the tools->start-up stuff set
correctly (but not yet turned into a mde, and not yet with the shift key
turned off, and not yet split), check out:
http://www.attcanada.net/~kallal.msn/msaccess/DownLoad.htm
Down load he 3rd example from the above. Give it a try. It is ready for
deployment...sans the split, and mde, and shfitkey by-pass
