>>What version of VFP?
>
>6 - sp3
>
>
>>There is a bug in 5.0 that would cause this. The fix was to add DODEFAULT().
>
>I'll try that, but WHERE do you add it?
>

When you subclass something and want to extend the functionality, you need to determine whether it supplements the inherited code or supplants the code. If it supplants (completely replaces), then your code should never execute a DODEFAULT, and in fact, if base class behavior should be filtered, a NODEAULT should be added to the code.

If my code enhances the parent class code, I need to decide if I filter out the conditions under which the parent class acts, or if I want to act after the default behavior. I use the following contructs:

*Enhance after the basic functionality is used
LOCAL uReturn
uReturn = DODEFAULT() && catch parent's return and save
DO CASE
CASE <i>something that this handles afterwards</i>
   *do some stuff
   uReturn = <i>whatever I want returned</i>
CASE <i>something else that this handles afterwards</i>
   *do some stuff
   uReturn = <i>whatever I want returned</i>
ENDCASE
RETURN uReturn

*Filter where the base code executes only when I don't
LOCAL uReturn
uReturn = <i>some default in case I get stupid</i>
*  If I want to block base class behavior, too, add a NODEFAULT
DO CASE
CASE <i>something that this handles instead of parent's</i>
   *do some stuff
   uReturn = <i>whatever I want returned</i>
CASE <i>something else that this handles instead of parent's</i>
   *do some stuff
   uReturn = <i>whatever I want returned</i>
OTHERWISE
   uReturn = DODEFAULT() && catch what would normally come back
ENDCASE
RETURN uReturn