--
Joan Wild
Microsoft Access MVP
Sorry, I meant that they could not open the file in the designer tool
without entering the password.
The database is not split. It is a standalone app and tables for
single user - the only security I care about is to disallow uesrs
seeing or modifying the tables, forms and code through the designer
tool.
You can create a mde from your mdb; that will not allow them to modify
forms/reports/code. (If you do this, be certain to keep your original mdb in
case you need to make changes). However for the tables, mde won't help.
You would have to implement security to keep them out of the design of the
tables. You can secure it without them having to log in. See
http://www.jmwild.com/SecureNoLogin.htm
Otherwise, you can hide a lot of the interface from them, but it won't keep
the determined out.
Backup your database; you can easily lock yourself out playing around with
these features.
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)
Click on the Advanced button and 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
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.
