Hi Fabio,
actually that works, because myClass.Init() creates an instance of itself in SomeControl.parent, so myClass.Destroy() doesn't trigger here.
But the concept doesn't work. I tried it and it doesn't work.
Evidently SomeControl.Destroy() doesn't execute because it can't get rid of the oMyObject.


>Hi Bill,
>
>I think this isn't ok.
>
>

>SomeControl.Init()
>  createobject( 'myClass', this ) && fire myClass.Init and myClass.destroy
>

>
>Am I correct in my assumtion that SomControl.parent.destroy() would trigger myObject.destroy() before SomeControl.destroy()?
>
>No
>
>Fabio