>It does the same on VFP9 Beta. If you rem out oTest.AddObject("oObj2", "form") it works, what are you trying to do here.

Yes. And if you rem out oObj1 and "show" oobj2, it also works. It's the combination that fails I.E.:

*Another version of FORM in CUSTOM which does not fail
Public oTest
oTest = CREATEOBJECT("custom")
oTest.AddObject("oObj2", "form")
otest.oobj2.Show
*EOP

F.Y.I. This is the stripped down version of a working application where there are many objects doing many things. Among other things, a mail monitor and progress bars.

Note, I have worked around the problem by creating properties instead of using ADDOBJECT. However, I really want to understand if this is a bug or if we are really not supposed to create FORMs in CUSTOM objects.

Charles Richard