>Hi Craig
>
>>If you put code in the Error method, it will override an ON ERROR routine.
>
>yup, I know 'bout that...
>
>>For a complete discussion of VPF error handling, see the whitepaper at www.stonefield.com.
>
>did. Can't find anything relevant.
>
>I need the code to stop AT the error - like it does when I'm debugging non visual code. I don't want or need to know what sort of error it was, other than what made vfp fall over. I need it to stop at the error so I can then check the value of sundry environmental variables there and then. As soon as the vfp error code is invoked, half the environment is immediately changed, making it very awkward to figure out exactly what is going on.

You actually want the default VFP behavior - the cancel-suspend-debug-ignore-help dialog? Then issue ON ERROR with no arguments at all, i.e. switch it completely off. You probably got some default error handler from FFC classes.

? on("error")

will give you the current error handler setting. You may even save it into a variable,
cOldErrHandler=on("error")
on error
[your code with no error handling comes here, including running a form]
on error &cOldErrHandler