I have a DTS process that executes nightly and processes some data. If there is an error (such as the source file being out of date), several notifications go out. Something that came to mind this morning was an idea to persist a variable between executions that would store the last execution's exit state. If the current execution detected that the pervious execution was a failure, but this one is successful, a second notification should be sent stating the error was recovered from.
I suppose I could just do something in an ActiveX script to hit the file system and read/write from a status file, but is there a more efficient (SQL driven) means?