>>>Put in a READ EVENTS for your login. If successful, CLEAR EVENTS,
> then READ EVENTS again. If login fails, just CLEAR EVENTS.
>>
>>
>Ok, it works now. What I did was to put my READ EVENTS in
>my form Activate() and the CLEAR EVENTS in the master class.
>The right way is to have the READ EVENTS in the form Activate()
>and the CLEAR EVENTS in the form QueryUnload().
>>
>>
>Each top level form need to have its own EVENTS.
>>
>>
>I guess I'll have to add a property in my base form which will
>take care of that by having a lTopLevel property in the base form.
>>
>
>>Thanks.
>
>
>Michel, I am having the same problem, I am going to put a READ EVENTS in
>the Activate(). When I use a form not saved as a class I don't have this
>problem. Will let you know how it works out.
>
>Thanks,

FWIW

Here's how I do this.

* logon
glContinue = .T.
DO FORM LOGON
IF glContinue
DO Main.mpr
READ EVENTS
ELSE
QUIT
ENDIF

So am I holding up other windows processing because there's
no READ EVENTS following DO FORM LOGON?

This has been my approach on the last ten systems or so (in 3.0,
3.0b and 5.0). No problems yet...

Larry Moody
developer in training (for about 10 years now!)