Bob,

This has got to be the biggest interface problem there is in the VFP development environment!

Since there is (was?) a known bug with DODEFAULT() and since the docs don't really say WHAT happens in the case of empty parent method but something in grandparent (or even empty there, but something higher) who actually knows what will happen. And I wonder what happens if you code DODEFAULT to sometho=ing which has a NODEFAULT in it?

All in all, seems to me the best hope is for some kind of improvement in the Interface for VFP 6 and leave DODEFAULT out of it (except in explicitly known cases).

Cheers (the chicken's way out, I know)
Jim N

>I have built a framework for a project that I am part of. As others create forms, they often write code in a method without realizing that it's parent has code that will now not run.
>
>There is a list of the methods with code in the framework, but it doesn't always get looked at. Sometimes, code is added to a base method that was previously empty. If one of the already written forms has code in this method, the new base level code will not run in that form.
>
>Question: How reasonable is the solution that ALL code entered into a form or control's method be started with a DoDefault(), even if the parent(s) of this method are currently empty?
>
>Bob