-----
This isn't formally documented behavior so I don't think I'd write a whole framework based on this short term exposure of the memvar.
-----

I don't think I suggested that anybody would.

I also don't know why you indicate that this behavior is not documented, formally or otherwise. From the DO FORM entry in the helpfile:

-----
If you omit the NAME clause, Visual FoxPro creates an object type variable with the same name as the form or form set file.
-------

This is what the product does, and this is how it's documented (has been since VFP 3 I think).

I know there were good reasons for them doing it this way in the first place, because of where people were coming from in the 2.x context. But now it's just confusing and it has a tendancy to have this effect on people's expectations.

>L<