>>My application exits fine and gracefully from the menu or by clicking the x in the corner of the screen. The problem is, I can't figure out how to exit from the login screen. An exit button with 'clear events' doesn't do the trick. Up until now, I thought I had a reasonable workaround; make the login screen modeless and just allow the user to click in the corner of the screen. The problem is, a modeless login screen allows the user to access the menu. No problem I say, so I SET SKIP to type("gcusername") = "U" on all the options in the top level. This should disable the menu until a login is successful. Well, the menu looks disabled, but if you click on it before you login, the SET SKIP for commands for the various menu option are evaluated (and returns an error because my global security level variables have not yet been set) even thought that pad is disabled. Even worse, after 'OK'ing out of all the error messages from the the unknown variables, the 'x' in the corner of the app
>>screen is grayed out, leaving no way to exit the app. What a mess.
>>I can't help but wonder if there is a better way to tackle all of this. All of this trouble could be avoided if the 'clear events' in the exit button on the login form worked. What gives?
>>
>>Thanks,
>> Erik
>
>make login screen modal.
>save login screen as class.
>in main.prg, oLoginScreen = createobject('login screen')
>oLoginScreen.show
>
>*- code continues here when window closes
>*- evaluate login attempt and continue if valid
>
>release oLoginScreen

How does this fit in with my goApp.show? Should my startup create and show the login screen first, and then, only if login is successful, create and show the application object? ie- should my login screen be a separate entity from the applicatoin instead of a part of it?
Thanks for your reply.