>>If this class is subclassed, and the subclass or the object also has code in the method--of course you're calling DODEFAULT()--the breakpoint won't work as is. You have to change it to use the form:
>>
>>The bp as is will work except under these conditions, or so far as I've been able to discern.
>
>Nancy,
>
>Thanks for the response.
>
>If I understand your point correctly, it sounds like double-clicking in a child class' code window to establish a breakpoint is essentially useless

Not necessarily. It just takes an extra step in the somewhat special circumstance I describe. Is that your situation, BTW? I'm assuming that what you're seeing is the case I run into.

> and doesn't work because of the syntax convention it uses to create the breakpoint. Is that correct?

The syntax is fine, I feel. It's that the debugger, for some reason, doesn't recognize the breakpoint when it get's to it through a DODEFAULT.

>I could be experiencing a weird flashback (not the first time), but I could've sworn this used to work.

Yes, you're right. It didn't used to have this problem, that I recall anyway.