Eeek! Sorry, Dragan, don't know what I did to that message, but I'll try again: Ahh, I see...I hit a "?" instead of ending the HTML tag. :( Okay the rest of that paragraph is in italics. (I hope!)

>Say you have (psuedo code):

>DEFINE CLASS Grandpa AS TEXTBOX
>PROCEDURE INIT
>  = MESSAGEBOX( 'Hi, we're in the myTextBox object init' )
>END PROCEDURE
>ENDDEFINE
>
>DEFINE CLASS Dad AS TEXTBOX
>ENDDEFINE
>
>DEFINE CLASS daughter AS TEXTBOX
>ENDDEFINE

>
>It is my understanding that the Grandpa object's init() *should* fire for the Daughter object since there is no code in it or its parent's method. Only if there is code in the daughter do you need a DODEFAULT in *her* init.
>
>As for the DOFAULT weirdness, I *think* I remember from a long and very interesting discussion somebody had with David Frankenbach, that if you have code in Daughter, and a DODEFAULT() in daughter and code in Grandpa, but the Dad.Init() is totally blank, then Dad won't "pass" the implicit DODEFAULT up to Grandpa.
>
>HTH