After you assign the NULL the object reference to the calling form does not exist anymore. If you don't do this your Form B may not be destroyed completely and will hang around.

>Nick, thanks for your reply.
>
>What exactly does assiging Null to the calling property form do, ot more omportantly, If I dont do it, what sort of problems am I likely to run into ?
>Regards,
>
>Gerard
>
>
>
>>Hi Gerard,
>>
>>This all looks OK. The only thing you need to make sure that you assigned
>>ThisForm.oCallingForm = .NULL. before closing the form, so there will be no dangling reference.
>>
>>>I am increasingly finding in my apps that I am calling a form from within another form, and am wondering is there any downside to the way I am doing it .
>>>I have seen references to 'dangling forms ' or 'dangling objects' but am not quite sure waht this means.
>>>
>>>I have a form (FormA) which Calls a form (FormB) and I am doing this as follows:
>>>
>>>1. In FormA I have a button which: Do Form FormB with This.Parent
>>> (This.Parent is it the parent of the click button .i.e. the Forma)
>>>
>>>2. In My FormB init I have a parameter and I store the called form to aproperty
>>> Init
>>> Parameters MyCalling Form
>>> This.oCallingForm = MyCallinForm
>>>
>>>3. This means that , inside in Formb I can access all proerties of FormA
>>> e.g. lcFormAcaption = ThisForm.oCallingForm.Caption etc.
>>>
>>>4. I close FORMB either as a Release Thisform or clicking on the 'X' of formb
>>>
>>>This all seems to work fine and I dont have any problems ..... but do I Have any leakage or dangling objecs hanging around afterwards... or maybe there is a better alternative ?
>>>
>>>regards,
>>>
>>>Gerard