>>But then, it can be safely omitted, because the nodefault/dodefault combination is unnecessary.
>
>The Dodefault() should be used especially if this object/class is more than one level away from the VFP baseclass, otherwise you lose any other inherited code.

That would surely happen, of course. But the parent code would fire even without... Oh, I got it now: the nodefault stops all code, native VFP and custom parent class code from running, and then DoDefault() calls the parent class code without the native VFP behavior. That makes sense (in case I got it right this time). I actually do that without much thinking all the time, but this time it seems I had better thought more before I wrote that.

Sorry if I confused anyone.