>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
Create a procedure that uses aerror() or any of the other functions to grab the error message and log the information to a table. Then issue ON ERROR command at the appropriate place at the top of the loop or just before the loop starts.
The any error that occurs will be logged to a table and you can deal with it later.
Eric Kleeman - EDS Consulting Services
MCP Visual FoxPro
MCSD C#.NET
Hua Hin Thailand
Los Angeles California