>Bill,
>
>Other folks have pointed you to the scope resolution operator. I would simply caution you that needing to skip the code in the parent is a very loud statement that the class is NOT a subclass of that parent but rahter a sibling class of that parent. This should cause you to take a clsoe look at your class design as it is not usual to skip levels of inheritence.

Hi Jim,
Maybe you can give me a better idea.

What I'm doing is sub-classing VFP's Foundation Classes. I'm trying to leave the FFC alone, so that future updates can just be swapped in, but now and then I discover a method in the FFC that doesn't do what I want and can't be corrected in the sub-class (simplest example: _HyperLinkBase.NavigateTo() has a "...Visible=.T." in it that I don't want to execute), so I have to re-write the entire method in my sub-class (without a Dodefault()), but I don't want to lose whatever is in the FFC's parent class.

The only thing I can think of is to skip over the level that I've re-written.

Any other suggestions?