Is there a better way to prevent a user from hitting F11 to view the
database window then setting the startup options?
Gee, I thought the startup options are quite good in this regards...
It seems to me
someone can copy the .mdb file and open it on another computer with
admin rights and get into everything.
copying a mdb to another pc does not change the startup options one bit...
copying a mdb to another computer does not eliminate, or effect the
workgroup security settings (assuming you are talking about security here).
If you secure the file with workgroup security...copying to another machine,
over writing the workgroup file...or creating another workgroup file will
NOT give you access to the file. This assumes you correctly setup security.
You most certainly can, and should hide all of the ms-access interface. The
options to complete hide and keep people out of the ms-access interface can
easily be done using the tools->start-up options. Using those options allows
you to complete hide the ms-access interface (tool bars, database window
etc). Also, using these options means you
do not have to bother setting up security.
Try downloading and running the 3rd example at my following web site that
shows a hidden ms-access interface, and NO CODE is required to do
this....but just some settings in the start-up.
Check out:
http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm
After you try the application, you can exit, and then re-load the
application, but hold down the shift key to by-pass the start-up options. If
want, you can even disable the shift key by pass. I have a sample mdb file
that will let you "set" the shift key bypass on any application you want.
You can get this at:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html
what is the best way to secure the backend data against such things?
Well, if you don't want to use security, then I use
I make a macro called AutoExec. In the macro, I put the following code:
Action Parms
Msgbox message:You do not have permissions to run this file
Beep: Yes
Type: Critical
Title: Can not run
Quit: Options:Exit
As an alterative, you an make a nice little form in the back end, and set
the startup options to run that form that displays a message, and then when
they click ok...you do a application.quit.
And, if you disable the "shift key", then that will keep most users out....
If your users are smarter..or well trained..then you will have to setup
workgroup security to get them out of the back end....
It is quite amazing how simple, and how well the above little macro
works!!! - it keeps most out!!!
