>>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.
>
>Not exactly.

I was too quick to reply - ten minutes later I went through it in my mind again and remembered that I said couple of things wrong... but I counted on you to come up with a proper explanation, which you did, and...

> And there were some changes to the way this worked between VFP5 and VFP6. I, and this is a personal opinion, don't think dodefault() should ever cause VFP BaseClass behavior to execute.

...actually added some things I never doubted existed. Thanks.

BTW, we seem to be neighbors no more. When did you move?