>I've got a program that is gonna take about a day to run. It's basically one big for/next statement that does the same thing about 20 times to different datasets. Since I don't want to wait around watching this thing for 10 hours....if it encounters an error I want it to simply move on the next data set and I'll figure out the error the next day. What I need is "on error loop" but that doesn't work. (Nesting error) Any ideas would be appreciated.
>
>Thanks,
>-Bob

Bob,

I think you have a situation where the RETURN TO [MASTER | ProcedureName]command would be helpful, if you organize your program appropriately. This would allow your error handler to pop the stack out of the offending sub-program and return directly to the main program, where the outer loop processing could resume. This sort of "localized Abort" is a useful general feature I've incorporated into my error handling classes (see http://www.ideaxchg.com/ix07/er/_sys/toccontu.htm).

Mike