>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.
>

Thanks Nancy. Thats a good workround, but it doesn't deal with the real issue - which is "why can't I get the damn thing to stop on the offending line in the first place." !

Harry