Thank you for answering, Gary.

The variables are still in scope. The problem is that I can see but cannot activate the spawned form because the main form is modal.

Alex


>Alex:
>
>You create a wrapper program to define your private vars and then you call a modal form. I assume that it is your called modal form that contains the button that that spawns the lookup form?
>
>If so, the private variables should still be in scope because they were defined higher up the stack. Obviously, you cannot be experiencing this otherwise you would not have posted this message. So, what have I misinterpreted in your explanation ?
>
>-=Gary
>
>
>
>>As part of a migration of a FOX 2.6 app, an automatically created wrapper program defines some private variables and then calls a form. Up to now, making the form modal has been good enough to keep the variables in scope for the life of the form and a small price to pay for automatic migration.
>>
>>Now there is wrinkle. The framework I use spawns a lookup form at the click of a button and I want to use it, yet not lose the outer variables.
>>
>>Is there another trick to keep those variables in scope and yet allow two forms? Maybe a getless read in the wrapper program (ugh!), creating a formset (ugh!), or some other way?
>>
>>TIA,
>>
>>Alex