To keep users out of our backend database we have a startup form that opens when the MDB is open. The only option it gives the user is to exit the database. All menu's are suppressed so this really is their only option, if they get to this form.
We have users that are opening our backend database by holding the 'shift' key at startup and changing data direclty. They have been told over and over not to do it and most have complied. However, I would like to eliminate the possibility.
I checked into password protecting the database, which is easy enough. I even made a test version of the app that works with a password protected backend. However, I have been repeatedly warned that there are many free and effective utilities for breaking the password of an Access database.
The option I am looking into now is disabling the 'Shift' key option on startup. This is very easy to do and I have code to do it internally in the MDB and I also found an MDB that will toggle the option externally on any MDB that you choose.
I have techiniques and code to implement both the password protect option and the disable 'Shift' option so I am not asking for those.
Due to the ease of breaking the password I am leaning toward disabling the 'Shift' on startup option.
My concern is that if something goes amiss I have also locked myself out of the database and would be much worse off that I was before. I have an external routine to toggle the 'shift' option and I will have a 'hidden' spot on the startup screen to also toggle the opton if I ever have to get in to the backend. I am still concerend about worst case scenario, the database is having issues and I am locked out also.
Again, I am not looking for coding solutions to these two options, I have those.
I am interested in what steps the EE developers recommend in this situation and what you have done to address a similar issue.
Are my fears of being permanently locked out of my own database by supressing the 'shift' on stratup option unfounded?