>Fred,
>
>NODEFAULT only prevents the VFP BaseClass behavior from occuring automatically at the end your overridden code. There isn't anything inconsistent about it at all. Sometimes though the BaseClass behavior can undo work you've done in method code in this case you can NODEFAULT, explicitly call it with BaseClass::Method() and then the rest of your method code.
>
>>There seems to be some inconsistancy in the way parent class code is executed, or at least in my understanding of it. Sometimes NODEFAULT is required to prevent the execution, other times, it is not.

David,

Thanks for the clarification. I was pretty sure that was the case (VFP BaseClass behavior) but I THOUGHT I had run into a couple of circumstances where that didn't seem to be the case. I may have been thinking of ActiveX methods/events, though. NODEFAULT does not seem to work there at all, at least not with the TreeView!