Thanks David, Jim and Barbara for this obviously vital knowledge about inherited baseclass code. All of this information leads to a few more questions of course...

From what I gather, it is a good idea, in general, to DODefault() in subclass methods that override inherited code, because generally speaking, one would be adding functionality to a special subclass. (btw, I wasn't overriding to prevent inherited behavior...just wasn't sure if my overriding was in fact preventing inherited behavior).

Now if what Jim says is true, the DODEFAULT() is not really necessary for methods inherited directly from VFP baseclasses because it will always be executed anyway...??? ... but putting it in, as part of 'good' general practice is a good idea??

You also say I may explicitly execute the DODEFAULT() anywhere in the modified method ... so I presume this let's me control when the 'default behavior' occurs?

All this control over default behavior presumes one has a good handle on what the default behavior is. So I ask again.

Is the default behavior for inherited baseclass methods explicitly specified anywhere in the official documentation?

Like the old 'Outer Limits' show...I want to be the one who controls the Horizontal and the Vertical. That means I need full access to the information of how to control it. Doesn't seem like too much to ask of a professional developers tool.