How to Reset Full Menu Option For Database On Startup

[AricC]

I have recently finished a DB (Thanks Adrian & Mary for your assistance), I have set the full menu/default shortcut menus to off for the startup etc.. I want to go in and make some changes but I can't figure out how to reset the bar to 'on' I'll post a SS to avoid confusion about the screen.

Thanks,
Aric

[NeoPa]

I'm not sure I follow what the problem is.
Isn't setting the Menu Bar and the Shortcut Menu Bar simply a matter of selecting from the dropdown boxes. I feel sure I must be missing something obvious here...

[AricC]

I have set the Full Menu etc.. to off when the DB is started. Now when I open the DB the menu's uptop are gone and I can't find a way to get the default back I've messed around with add/remove buttons with no luck.


Thanks,
Aric

[ADezii]

I have recently finished a DB (Thanks Adrian & Mary for your assistance), I have set the full menu/default shortcut menus to off for the startup etc.. I want to go in and make some changes but I can't figure out how to reset the bar to 'on' I'll post a SS to avoid confusion about the screen.

Thanks,
Aric

CTRL+F11 should bring back the Default Access Menu Bars then you should be able to handle things from that point on. Also, look for an Application.MenuBar = "Some Menu Bar" in the code which would have the effect of loading a Global Menu.

[NeoPa]

I have set the Full Menu etc.. to off when the DB is started. Now when I open the DB the menu's uptop are gone and I can't find a way to get the default back I've messed around with add/remove buttons with no luck.


Thanks,
Aric

So you can't actually get to the Startup screen at all atm?
Not good.
There are some tricks to try but it is possible to leave a database completely protected if you're not careful and never be able to access it again.

• Try holding down the bypass (Shift) key while opening the database.
• Try using Ctrl-Break while the system is running to see if it will allow the operator into the Debug window.

Whenever protecting a database like this always leave yourself a back-door. I know this is a bolted horse scenario but it won't hurt to make the point anyway.
Let me know how you get on.

[Rabbit]

Make sure you hold that shift key till it opens fully. When someone first told me about the bypass key I let go of the bypass key too early and it wouldn't open up with full menus.

[AricC]

So you can't actually get to the Startup screen at all atm?
Not good.
There are some tricks to try but it is possible to leave a database completely protected if you're not careful and never be able to access it again.

• Try holding down the bypass (Shift) key while opening the database.
• Try using Ctrl-Break while the system is running to see if it will allow the operator into the Debug window.

Whenever protecting a database like this always leave yourself a back-door. I know this is a bolted horse scenario but it won't hurt to make the point anyway.
Let me know how you get on.

NeoPa,
Shift(Bypass) method worked!
What settings do you recommend?

Aric

[NeoPa]

That all depends on how secure and how convenient you want it to be.
I generally don't need to secure my databases that well - my userbase is either trustworthy (One colleague & me) or too incapable to pose any threat.
However, I have worked on projects before that did and they were well closed up but with a label which had a Double-Click event which showed the database window.
The fundamental rule is :
Don't lock it down to a level unless you've tested the code to let you back.

I haven't done detailed work in this area for some time but if you want help writing the code then I'm sure I can dig around and help get something together.

[AricC]

I think I will just leave it the way it is there is no way they know about holding the shift key to open fully. Great advice thanks!