>Actually, the only way (since VFP 6.0) that you can reliably cause the base class behavior to execute first, is by using the scope resolution operator. Something like this:
>
>

>Textbox::GotFocus()
>This.SelStart = 0
>This.SelLen = 999
>NODEFAULT
>

>
>followed by you custom code and finishing with a NODEFAULT.

Is the above true because you are dealing with the general case where the above code appears an arbitrary number of steps down the class hierarchy?

Or is there some other VFP6.0 subtlety that prevents the bass class behavior from being executed by DODEFAULT() even when you're subclassed directly to a base class?

Normally, I would try to design so that subclass methods only add to the functionality of the parent - so I'd expect a DODEFAULT() to always execute the baseclass code, assuming that any parents up the hierarchy also execute DODEFAULT() if they actually contain code.

Is there any reason I shouldn't expect the default bass class behavior to execute when I issue a DODEFAULT() and none of the methods up the parent hierarchy contain code?