> Unless I greatly misunderstand the concept of scope, or lifetime, of a memory variable, once the memvar is gone - so is your form's reference (as may be your form object); and if it was LINKED - the object is gone as well (for sure). Thus, saving the name of an object created in a procedure on runtime in whatever container (table, custom class' object) loses meaning if this name/memvar is not visible enywhere in the program; that latter calls for PUBLIC memvar.
>
You misunderstand the concept of scope. When you instantiate an object, it has (somewhere internal) a reference counter. When you store another reference to that object somewhere other than the original variable, the variable going out of scope doesn't destroy the object.
Tamar