>>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?
>
>It's mostly reasonable, with the caveat that you might actually want to
>override the method, rather than supplement it, in which case you don't
>want it. Also, there's a known bug involving DODEFAULT() and grandparent
>classes: check the MS Knowledge Base for details.


Wasn't that bug fixed in 5.0a?