Chris,

NODEFAULT has no effect on any of the code you put along the class hierarchy. NODEFAULT only controls the VFP baseclass behavior that normally executes at the end of the event. NODEFAULT is useful if you need to prevent the VFP baseclass handling of the event all together or want to invoke it earlier than it normally occurs and prevent it from occuring again later.

If you override a method with a single line of code:

NODEFAULT

You are indirectly overriding higher up code because you are not calling it via a dodefault() or :: scope resolution operator based call. But you aren't NODEFAULTing it. It's kind of a fine line of distinction I wanted to interject into the thread.

>It was something in the form class that i thought i had been NODEFAULTing.