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

>I have been getting a c0000005 error in an application which has worked fine until recently. I was finally able to strip it down to bare minimum and the resulting code below will generate the error.
>
>It has been confirmed on in VFP 8 SP1 on
> Windows XP SP2
> Windows 2000 Pro SP4
> Windows 2000 Server SP4
>
>Can someone tell me why this error occurs and why now? There are no known modifications to the structure of the application to justify this. My client needs delivery soon and I am at my wit's end.
>
>Is it illegal to add a FORM to a CUSTOM object? If so, why does VFP not complain at creation? And why does no error occur if for example, the property sheet is active during the running of this code?
>
>TIA
>Charles Richard
>
>*Generate a c0000005 error
>*---------------------------------
>Public oTest
>oTest = CREATEOBJECT("custom")
>oTest.AddObject("oObj1", "custom")
>oTest.AddObject("oObj2", "form")
>oTest.oObj1.AddObject("oObj3", "form")
>oTest.oObj1.oObj3.Show
>*EOP -----------------------------