>>

>>Application.Visible = .F.
>>SET SYSMENU OFF
>>... setup stuff ...
>>DO FORM frmLogin.SCX
>>READ EVENTS
>>... as user logged in, go on with the setup and get user input ...
>>SET SYSMENU AUTOMATIC
>>DO menMain.MPR
>>READ EVENTS
>>

>

ôi, Alonso,

>As far as I know, the first read events will "stop" program execution and make VFP start receiving windows events. In this case, the SET SYSMENU AUTOMATIC and everything after that wouldn't be executed.

That's half the point. Allan wanted the login form to be fully processed before anything else. Program will resume execution of next lines after the CLEAR EVENTS in the destroy method of the form.

>I do the same thing in other way. Untill the DO FORM frmLogin.SCX it's basically the same. But I place my READ EVENTS in the Login form, and everything that has to be setup after the user is logged, is made from a method of the Login form.

I believe both are basically the same way: it's a matter of style to put the READ EVENTS instructions in the form or in the calling (main) program. To me it is clearer when it stays in the program.

>Maybe I'm wrong, but I remember having some trouble with a missplaced READ EVENTS.

Missplaced READ EVENTS, like any other missplaced code, surely can get us into trouble ;)

bye