>Bruce,
>
>LINKED is just a way of giving a memvar name to the form object. That memvar still has scope as you've found. If you are trying to get two forms to cooperate with each other you might want to try:
>
>do form Child with thisform linked oForm
>thisform.moChildForm = oForm
>
>where moChildForm is a parent form property, the child form can also keep it's own link back to the parent form with the reference you passed to it. They can use these links to make callbacks to each other. For instance when the child form wants to close it might:
>
>this.moParentForm.CallingToLetYouKnowImOuttaHere()
>
>in it's Release() method. The Parent form can then:
>
>* Method CallingToLetYouKnowImOuttaHere()
>this.moChildForm = .null.
>
>If you are trying to come up with a generic use child form/object you might want to use another control, like a button, that launches the child form as the link maintaining object so you aren't placing restrictions on the forms that can use the child.

Thanks David...So the LINKED can actually serve a prupose, I see. I think your idea here is what I'm seeking: a smoother way for forms to communicate without publics, or the somewhat unaesthetic method of using the forms collection...I'll try implementing it tomorrow.