Hello David.

>> However, as Gerry S pointed out, explicitly executing DODEFAULT in the subclass does cause the default behavior to execute twice (if you do not specifically use NODEFAULT)

This behavior lacks class! (IMHO) <<

I hate to disagree with you here, but < s >...

DODEFAULT() calls up the class hierarchy and executes the code (if any) in that method in the parent class.

Native VFP base class code runs after your custom code (if any) in the method.

So if your custom class is directly subclassed from a VFP base class, and you have custom code in a method that includes a DODEFAULT(), the code of the parent class (the base class) gets executed. Then, at the end of your method, the base class code gets executed as usual.

By design (IMHO).

Marcia