David,

>I see. It looks as though most of the objects on the Form Controls Toolbar of the Form Designer are built directly from VFP Baseclasses (Their class is equal to their baseclass), so theoretically adding DODEFAULT would be redundant in any of these...if I understand you correctly.

You can click the Books button and put whatever classlib you want on that toolbar. Frankly though I find it unuseable because it's impossible to know one button subclass from another without hovering the mouse and wait for the tooltip to appear. I tear off the All tab of the project manager and drag my classes out of there. Tools, Options, Field Mapping allows you to assign default classes to use for each field type. You can also specify classes at a field level in the DBC.

Dodefault works rather erratically for the baseclass behavior, but fundamentally it's not needed because of the automatic call VFP is doing behind the scenes.

>>>Is the default behavior for inherited baseclass methods explicitly specified anywhere in the official documentation...
>...Doesn't seem like too much to ask of a professional developers tool.

The documentation isn't perfect, it is getting better. Resources like the Hackers Guide and the FoxForum Wiki site can help fill in the gaps.