>Actually this form is a test harness for a container class, it is not a form class, so I am launching it with a DO FORM rather than a CREATEOBJECT. I find it curious that the form leaves a variable behind when it closes. It is not the behavior I would expect from a native FoxPro object.

Yes, it leaves something so it's always more convenient to link it to known variable/property: DO FORM ... NAME oApp.myform LINKED
I've read your reply to David, and I guess the reason is in another VFP area: its grids used to forget their definitions, so it's better (and sometimes necessary) to wake them up programmatically by firing a method (Myform.Resetgrid) conaining all grid settings.