>>Tamar,
>>
>>ShowWindow is 1 for form b, set at design time in my data_filters form class.
>>
>>
>>>>I am working with Top Level forms for the first time. The following code is called from a button on a form, form a where showwindow is 1 - in top level form. Also, I just realized now, as I was writing this, that "form a" is modal. If set step is on, upon executing newobject, the debugger goes to the first init of the first object and executes it, then returns, then executes the following lines of code, but form b never becomes visible. If I take out the set step on, everything executes just fine.
>>>>
>>>>
>>>>
>>>>
>>>> SET STEP ON
>>>> thisform.l_filter_was_called=.t.
>>>> *DO FORM forms\form-b TO x
>>>> thisform.ofilterform=NEWOBJECT("data_filters","data_filters")
>>>> thisform.ofilterform.filter_controls[1,1]="curdata"
>>>> thisform.ofilterform.filter_controls[1,2]="curdataunfiltered"
>>>> thisform.ofilterform.filter_controls[1,3]="accountnam"
>>>>
>>>> thisform.ofilterform.show(2)
>>>
>>>What is ShowWindow for form b (which I assume is the one you're storing in Thisform.oFilterForm? It also needs to be 1-in top-level form.
>>>
>>>Tamar
>
>What happens if you pass 1 to Show instead of 2? Calling a modeless form from a modal form is pretty strange.
>
>Tamar

If I pass 1 to Show it doesn't make a difference. In fact any combination of modal/modeless for either form doesn't make a difference. If the set step on is called BEFORE the call to instantiate the form - as in my example, then the form never shows. However, if I put the set step in the load or init of form b - then it is fine. I thought that maybe it was behaving like a browse would in a top level form - i.e. that it would show in the screen instead, but when I set application.visible=.t. it didn't make a difference.