>Nancy,
>
>The bug in 5 is that dodefault to an empty parentclass causes the baseclass code to run twice. This seems to be fixed in VFP6.
>
>>>As for the DOFAULT weirdness, I *think* I remember from a long and very interesting discussion somebody had with David Frankenbach, that if you have code in Daughter, and a DODEFAULT() in daughter and code in Grandpa, but the Dad.Init() is totally blank, then Dad won't "pass" the implicit DODEFAULT up to Grandpa.

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.