>>>>I am using an application framework similar to the sample to launch my forms with the launchform method from the application object:
>>>> oapp.launchform("mjrdetail")
>>>>
>>>>Within the form I do:
>>>> omjrsrch = CREATE("mjrsrchfrm")
>>>> omjrsrch.show()
>>>>
>>>>If the class mjrsrchfrm is modal, it shows and becomes active, but the mjrdetail form remains on top -- it won't go behind. If the class mjrsrchfrm is modeless, it just flashes up, then disappears.
>>>>
>>>>I know I am missing something major here in how these stupid objects are supposed to work together. If someone could take pity on me as a VFP newbie and point me in the right direction, I would be greatly appreciative.
>>>>
>>>>With tears of frustration,
>>>>
>>>>Valerie
>>>
>>>What is the setting of the Always On Top property? You also need a READ EVENTS to keep the form from flashing.
>>>
>>>Craig
>>
>>Always on top is set to false.
>>
>>I don't understand -- I have a READ EVENTS in affect from the original startup program. Do I issue another one when I instantiate the new class?
>>
>>Valerie
>
>check the alwaysontop property in the calling form, not the second one. the second one must be modal or processing continues on the next line in the code in the first form.

Thanks Dave. I've managed to figure out what was happening. I had the desktop property set as true on the calling form, so even if the second form was modal, the calling form remained on top. I think I understand the whole READ EVENTS thing now -- I would have to issue another READ EVENTS inside the calling form OR create a form based on my mjrsrchfrm class and launch it with oapp.launchform(), right?? What is the preferred way to do something like this? Is there any detriment to having multiple READ EVENTS (or really, I'm talking about stacked READ EVENTS aren't I). Is there any limit on them?

Valerie