What you're seeing IS standard behavior, but it's clear most folks are still not using the Error method in favor of ON ERROR. As, I think, Craig B. pointed out, "If you put code in the Error method, it will override an ON ERROR routine." This should be expanded to say, "It you put "*" in the Error method, it will fire and it will be the Error Handler!"
The only way to make it go away in VCX type classes is to ResetToDefault all Error methods! If you have PRG class definitions, you can do this:
#IF Development
PROCEDURE Error
LPARAMETERS ....
ENDPROC
#ENDIF
but for classes the only option is to clear the Error Methods.

>Clearly this is non standard behaviour and something in my environment must be causing it. I'm sure it will turn out to be as stupicly simple as my "CTRL F" problem was, but I just can't see it!
>
>I've also tried creating a new form with just 'on error' and a call to a non existent method in the load. No difference.
>
>
>Harry