I think it's reasonable to always use DODEFAULT() unless you want to override the method's default behavior.


>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