S
Stefan Drissen
Guest
Peter Judge You can – as an alternative or workaround – set a breakpoint on error (any or any number). From memory, you can do this in the Breakpoints view in the Debug perspective. This will effectively do what you want (ie stop execution when the error occurs and keep program/stack state). Now that looks interesting! Thanks! The 'any error' option seems a bit over zealous - a FIND tt NO-ERROR also fires an 'error' when the record is not available - but 'any unsuppressed error' seems to do the trick! Just need to ensure the debugger is fired up and breaking before any errors fly along.
Continue reading...
Continue reading...