Hi Rob ---

What you are trying to do maybe simple, but when explaining your problem using the specific properties of a certain object, it's hard to get a grip on the big picture on my end :-)

Why don't you reply with a general idea of why you're doing what you're trying to do and we can work through some alternatives?


>Your approach works fine if the application is run from within VFP5, but there are some mitigating circumstances which I didn't mention in the original post.
>
>1) This application is needs to run as a stand-alone and I am not showing the main VFP window, so having ShowWindow for MANSHI set to default (in screen) doesn't allow it to be visible.
>
>2) I'm hiding ORDR before showing MANSHI, so I can't have ShowWindow set to In Top Level Form either, as the top level form is hidden.
>
>I think you're right that a thinking shift is required. It seems that what I'm trying to do is a very simple thing. Your help is appreciated.
>
>Thanks,
>Rob
>
>>Rob ---
>>
>>Maybe a thinking shift is required here. By definition, a top-level form is modeless and acts as a parent to child forms. Maybe what you want to do is leave your WindowType=Modal, set Desktop back to .F. (this is not a desktop form, it's a child of ORDR), and reset ShowWindow to default. Then look at changing the AlwaysOnTop property to true.
>>
>>
>>
>>>I'm calling screen MANSHI from the Click method of a button on screen ORDR. I want the user to interact with MANSHI and close it before the code in the Click method continues. I have set the following on MANSHI:
>>>
>>>WindowType = 1-Modal screen
>>>ShowWindow = 1-As Top Level Form
>>>Desktop = .T.
>>>
>>>Regardless, the Click method continues execution and wreaks havoc. There are two other screens sitting in the background (besides ORDR) as top level forms that have been hidden.
>>>
>>>Any ideas why this is happening? This is making me bonkers!
>>>
>>> TIA,
>>>Rob