Hi Ken

>Can you put a deliberate error into a form? One easy way is to put something like this in INIT: =EVAL(m.ThisVariableDoesNotExist). This works because it will compile OK but crash at run-time. Then run the form.

>
>Now, exactly what happens?


as I've just explained to Dragan, instead of crashing on the offending line (I can step through the guilty line and watch this happen), despite having defused the error handler, [on("error" returns a null string throughout] the code leaps to the error method for the form where I've inserted a nodefault in the attempt to stall it. It then protests 'no parameter statement found' and crashes in the normal way - i.e. at the offending line! Trouble is the offending line is now the first line of the error method and not the code line that caused the jump in the first place.

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