>I created a top level form for my identification form where the user has to enter a password to proceed.
>
>This form is called at the end of my setup. If the password is ok, we proceed and give the user access to the menu otherwise the user might retry or quit.
>
>I created the top level form because I only want to see this form during the login process and not the menu and the main application window.
>
>By default, my CONFIG.FPW have SCREEN=OFF and I show the splash screen until the identification form is called. If the user succeed with the password, I have _screen.Visible=.T. so the application window appear.
>
>My question is related to the READ EVENTS. Before having a top level form, I was having the READ EVENTS after the identification form. But, now that I have a top level form for my identification form, if I don't have a READ EVENTS before, it will show up and disappear immediately.
>
>Where should I put my READ EVENTS or should I have two?

Michel,

I believe 1 read events is all you need. The idea if the code that follows comes from the Tastrade program. In my main program I instanciate my nonvisual class called *application*. In the init event I check to see if the user wishes to show the splash screen or just continue onto the login. Once the user successfully logs onto the system, the program returns to my main program and I return to my application DO() method. (After a successfull logon would be a good time to make your screen visable) Here is where I push my menu and READ EVENTS. No sense in reading events until the first requirement is met. Hope I understood your question properly.

Primitive but HTH

Jon