One useful tactic is to hide the Database Window at Startup ... look in your Options.
This will keep most users from seeing the database objects but it is not failsafe, not least because if your users have a full licence of MS Access on their PC they could easily get into Design mode on a query, form, or report with a right-click.
The safest method is perhaps to issue the database under a 'Runtime' licence. This protects the entire database from changes. There are oodles of threads on how to build and issue a 'Runtime' database within this Forum.
One useful tactic is to hide the Database Window at Startup ... look in your Options.
This will keep most users from seeing the database objects but it is not failsafe, not least because if your users have a full licence of MS Access on their PC they could easily get into Design mode on a query, form, or report with a right-click.
The safest method is perhaps to issue the database under a 'Runtime' licence. This protects the entire database from changes. There are oodles of threads on how to build and issue a 'Runtime' database within this Forum.
The easiest way to protect your code is to design a module and go to Tools > DB Properties and click on the Protection tab and set a password to prevent users accessing your code. It also prevents items form being exported/imported from/to other mdb's
With any of these strategies, it's really important to make a backup of the database before proceeding. Or test the changes on a copy, otherwise you may find yourself locked out, and unable to develop the thing any further.
Thank you all for the answers and advice. I have already tried the Shift+open. It works! (of course) I will try the other solutions as well to see the options. Again: Thanks.
Ps.: Does anyone know how to hide (and show) the menu bar: File - Edit - View - Insert etc.?