Harry-

One way to do this is that when you hit the error and suspend, use the debugger window's call stack to move back a procedure. You should have the offending code available in the trace window. Double-click the line of code to set a breakpoint on it (or several lines before possibly), then restart the program, cancel. Then rerun the code. It's pretty simple and works well, I find.

HTH

>apart from 'on error' or 'on error 0' what else must we do to prevent vfp jumping to its error reporting code rather than stopping where we want it stopped - on our offending line of code.