I always use the LINKED keyword so that the form is always available as long as the object type variable is alive. When I want to release the form, I check for the existence of the variable and if it is an object type and !ISNULL I issue the form's release method and if it is .null. I just release the variable instead.


From VFP HELP:


NAME VarName [LINKED]
Specifies a variable or array element with which you can reference the form or form set. If you specify a variable that doesn't exist, Microsoft Visual FoxPro automatically creates it. If you specify an array element, the array must exist before you issue DO FORM. If the variable or array element you specify already exists, its contents are overwritten.
If you omit the NAME clause, Visual FoxPro creates an object type variable with the same name as the form or form set file.

Include LINKED to link the form to the variable associated with it so that the form is released when the variable goes out of scope. If you don't include LINKED, a form can still be active, even though there is no object variable associated with the form.



>This call from a parent to a child form. Does the linked link them together somehow?
>And why do you use an alias of omyform?
>DO FORM myform NAME omyform LINKED
>
>Thanks
>Steve