I dont think thats the only way to do it.. If you ever installed a app that uses access tables to store the data and you try and open the database directly from the app directory, it will prompt you for a password no matter if you try and import or hold down the shift key..
That would be the user level security that I mentioned.
Personally, I've never used it so I can't advise you on how to set it up. Read everything in the Access help file on the subject and also do a keyword search here in these forums. I've seen several threads and faqs on setting up security. It should be enough to at least get you started. Maq
<insert witty signature here>
The following closes down pretty much everything, and you can start up your own form from autoexec macro.
I run this procedure in the first form opened to disable all. On that form you can log in and then this procedure is run to enable all. After that you can close the DB and then open it with shift.
Obviously the tables in the database can still be imported in other databases. In my case this is fairly useless because the only thing users could get out of this is an encrypted password. Decryption is done in VB, and that's password protected.
I wanted a program that could startup without the need of selecting any name or inputting any password.
(It is a DB that registers sales/stock etc. of the bar of a scout group).
As far as i know it is quite secure by now anyway, except if users that can login to enable the buttons are shouting around their password. Only other possibility is that somebody cracks the Password encryption, which offcourse is possible because it is only a bunch of sting manipulations tied together to get a text that is not comparable any more to the original characters or length of the password.
Public Sub EnableProgramming(hEnable As Boolean)
Set dbCurrent = CurrentDb
dbCurrent.Properties("StartUpShowDBWindow" = hEnable
dbCurrent.Properties("StartupShowStatusBar" = hEnable
dbCurrent.Properties("AllowSpecialKeys" = hEnable
dbCurrent.Properties("AllowFullMenus" = hEnable
dbCurrent.Properties("AllowToolbarChanges" = hEnable
dbCurrent.Properties("AllowBuiltInToolbars" = hEnable
dbCurrent.Properties("AllowBypassKey" = hEnable
End Sub "In three words I can sum up everything I've learned about life: it goes on."
- Robert Frost 1874-1963
That means you're trying to delete a property that doesn't exist. Did you disable the shift key before trying to re-enable it? If not, then that's the problem. Maq
<insert witty signature here>
Why deleting the property if setting it to false does the same thing and avoids the "Item not found" error. "In three words I can sum up everything I've learned about life: it goes on."
- Robert Frost 1874-1963
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.