Rick

Yes, the bug still exists in VFP5 build 415. This one involves double execution of the VFP BaseClass behavior if you DoDefault() to an empty ParentClass method. You will only see the effect if you are using a method like KeyPress() where the BaseClass does something discernable from the outside. In this case it inserts two characters into a field instead of one. If you look at the txtDate class on my website you can see what I'm talking about.

You are probably thinking about double execution of overridden GrandParent method code when a GrandChild class did a DoDefault() to an empty ParentClass method. This bug was fixed in VFP5 SP1.

>>Dave, are you sure about this? VFP 5.0a SP3 does not seem to exhibit this behavior. If memory serves, this was a bug in VFP3 that was corrected in 5. I don't have 3 installed anymore, though, so I can't check it out.
>
>Or perhaps it was in the original release of 5 and was fixed in 5.0a. IAC, it seems to work OK in build 415.