>Thank you very much for taking the time to respond to my post. I apologize my post wasn't clearer.
>
>I believe you correctly understood my question. My parent form called a modal child form passing a parameter object to the child form and back again. Yes, you are quite correct, the parameter object is indeed passed by reference. This, of course, can have significant implications. DO FORM..., here, does not require a TO clause.
>
>My need/interest here is simply that I want to be sure that certain object references are properly released and so I am explicitly releasing them.
>
>I find to remove object loParameters.SearchOptions, rather than the RELEASE command, the syntax I need to use is:
>

>	loParameters.RemoveObject( "SearchOptions" )
>

>(The TO clause was not the culprit here.)
>
>Remaining question: I am still unclear regarding the following scenario:
>

>	oObj = NewObject( "Custom" )
>	oObj.NewObject( "oChildObj", "Custom" )
>

>Given the above, would oObj.oChildObj be correctly released by simply assigning .NULL. to oObj? Do you happen to have insight here?
>
>Thanks again!
>
>Spence

AFAIK (not sure) you need to release child object first. E.g. oOBJ.oChildObj = null
oObj = null