In my method, you don't have to wait for the form to be unloaded to have access to the variables, the first screen can make use of the information while the second form is still open.

Bob

>Ok, yours and Christoph's ideas are good. How should I choose? Is there an advantage of one over the other or is it just personal choice?
>
>>The way I like to handle this is to put those properties an the original form, and populate them from the second form. When you launch the second form, in the load, make an object reference to the first form using something like
>>
>>THIS.oCalledFrom=_SCREEN.ACTIVEFORM
>>
>>Then use
>>
>>oCalledFrom.MyProperty=...........
>>
>>Then the value is already on the first form when you return
>>
>>Bob
>>
>>
>>>Maybe I'm just tired, but I have Form1 with a button that calls another Form2 just to gather a couple values from the user. Then I want to take those values and continue on in the button click code on Form1. I have Ok and Cancel buttons on Form2 that return either .T. or .F. respectively. How can I keep the other values gathered from Form2 in scope, or return them to Form1? Something simple for now would be nice.