The specific location is important for NODEFAULT.

When this is issued in an event, the default VFP code of the event doesn't fire. It doesn't have any effect on user code inherited from parent classes (which one might be led to believe by the name).

It's commonly used in KEYPRESS to prevent VFP from processing a keystroke as it normally would. There are some other specific uses for it.

The keyword can be included in a conditional statement, and used anywhere in the event code. At the end of the event, VFP evaluates the situation, and if a NODEFAULT has been issued at any point during the event, it will not process.

I've never heard of that being used in a CLICK method. It's possible that could have prevented the 2nd user method from being called. Is that the problem you ran into?

Jay