>>
>>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

desktop would have been my second guess. i don't use it because of problems like this. i don't know of a limit on the number of read events, but it's better to just use one if you can.