Mike,
I am a little confused by your reply. Do you mean that if I edit the class and press any key while it is open and then save it, then the default will no longer fire. Or do you mean that if I edit the class, do not hit any key, and then save it the default will no longer fire.

I understand that a space, tab, or enter key will fool the compiler into thinking something is there, but when I opened this the cursor was blinking at the end of the parameter with nothing in between. In any case, this is a good argument for requiring something like an 'override' keyword. The 100 or so customers that downloaded this update will have a difficult time understanding that their application no longer functions correctly even though no code was changed ( at least not willingly ).

I just looked at the code in the class browser and in the old definition of the grandchild class there is nothing except the class name. However, in the version that I sent out on Monday there is the recal function with a parameter. This is really really a bad feature in VFP. I certainly did not indend to do this and the interface did not tell me that I had.

We are struggling with rewriting our app. I have been doing fox since 1989 but it may be time to move to a compiled language that will enforce good programming habits.