DJ,

To add to what Wayne, Nick and Alan already said *g*

Back in VFP3 we only had the :: scope resolution operator and so the calls to the parent class became inexorably tied to the ParentClass name and method name like:

Textbox
   aTextbox
      bTextbox

in bTextbox you had to explicitly code aTextbox::SomeMethod()

With dodefault() these hardcoded name dependencies go away.

>I have seen this in articles, and coding all over the place. I have no idea what it means, when I should or shouldn't use it, or if it is even required.