>>but as I said in another thread here are 2 more ways :
>>
>>One option is to instantiate the form inside a container object
>>(a formset or an application object) and have the form set a property in
>>that container before it releases (e.g in the Destroy() event or in somecases in the QueryUnload() event)
>>
>>another option is to create some sort of a DoForm function
>>and add a guRetVal property to ur forms which will hold
>>the return value
>>e.g.
>>
>>FUNCTION DoForm
>>  LParameter tcFormName
>>   Local loFormInstance,luRetVal
>>   loFormInstance=CREATEOBJECT(tcFormName)
>>   loFormInstance.show()
>>   luRetVal=loFormInstance.guRetVal
>>RETURN luRetVal
>>
>>note: that u will have to hide the form instead of releasing it
>>and the form will be released when the DoForm function return
>>as the loFormInstance variable will be releases (automatically)
>
>Arnon
>
>Ok McGyver can make an atomic bomb out of a toaster! (s) What ever happened to simple explanations? (s) Yes Arnon can do anything but is the work worth the benifets?
the work is done only once, u incorperate the function into you application class or something like that and that's it
this way u don't use global vars.
I mean a Global var is simple & easy & quick but I was going by the MS recommendations & documentation. Shheeessshhh!.... (g)
MS limits you to modal forms...


Arnon