First, thanks to Ray for some issues he has resolved off line.

But now, I could use some guidelines about the use of Application Menu, and making Menu buttons invisible with security.

I have a Menu Page with 10 buttons.  This page is StartUp Page in Application Manager screen.
I have code that makes 6 invisible to all but @Group = "Admin".  Admin members see all 10, others only see 4.  This code is in FormEntry for the Menu Page.

Problem:
When starting application, Menu Page is visible with all 10 buttons, Login screen is visible.
After logging in, visibility does not change, (form is already open and visible before login).
This causes two problems for me: 1.  I don't want non-Admin to know about other buttons/functions.  2.  Invisibility does not run.
So, I changed the six admin buttons to be invisible as default.  That solved the first issue, the admin buttons do not show when the login screen comes up.  But after login, the Invisibility code does not run again , form is already loaded?
So, I tried putting the Invisibility code in Application Manager but that failed "Test" because the CommandButtons did not exist.

------------------------------
So, how do I trigger the code to change visibility of elements on a form that is loaded from the Application Manager?  I tried FormReveal as a trigger, but that also did not work.  I am looking for a solution that does not require any mouse or keyboard action to present the Menu with the Visibility Code executed.

And as a general comment, I would prefer that that form not even be made visible until after login has been authenticated.  Changing that timing would also probably solve this problem of code not executing because event has already happened.

Now that my Menu Form is the "Application Form", only the buttons work OnEnter, as you mentioned above.

What was not mentioned is that none of the menu Accelerator Hot Keys work.  When the form is loaded normally, the Hot Keys work fine, but when used on Application Menu, the button flashes, but the program does not execute. 

I think that this should be corrected to enable Accelerator Keys to function.  I suspect that in most cases, the Application Form will usually be a Menu Page.

Maybe in 2.0.4?

Thanks Carl

You are correct, I really expect the Accelerator keys to work right away. Ah, it's probably the old "focus" issue.  Need to do the first click to get focus on the form.  Click on the button does not do both focus and click.  But this requires using the mouse.  Want to try to stay with keyboard only.  How to get focus on form so Accelerator key will work?

Re the code in GlobalCode section:
How are you triggering the code?  Did you make a sub routine that is called by FormName/OnFormEnter?

To hide the Main Menu until after login, I am now using a Welcome Form that shows during login.  And it has one button with Accelerator key that continues to the Main Menu.  So I have handled the "hide the application during login" issue, but still want to get to Main Menu from keyboard.  Will have to play around some more.  Not a killer problem, but like a smooth GUI.  Don't like moving back and forth from keyboard to mouse.

The "large box to cover the entire form" idea works!

I created a filled box (filled with same color as the form background) which covers the entire form, set it to a layer higher than the rest of the elements so that it always covers them, and added a Visibility() command to Global Code (right next to the section that hides the other command button).

This stops the elements that you want to keep out of sight, from briefly displaying before and after the login process. The following code is what I used to test this idea.

Stat sYear as String = @GlobalValue("CurrentWorkingYear")

Label(Add, sYear + " Deposits")
Visibility(Search, 0)	// Hides a Command Button
Visibility(Box1, 0)	// Hiding Box1 reveals the other form elements 

I was never able to catch a glimpse if the "Search" command button. So, you could use this method instead of the welcome screen to keep the secret buttons/elements fully hidden.