Thanks Ted - a good question! Is there any other way? I've set it up so it displays a screen with the log scrolling on the screen and a countdown to the processing starting so that the user has some indication that it is running if they look at the screen during the day and has the opportunity to stop the app if necessary.
Perhaps my best bet might be to put the simplest form of shutdown routine in the error handler code - what would you suggest would be the simplest? This is an area which has always caused me some confusion; I tend to put everything into it to be on the safe side. It still leaves the question - why does it not jump straight to the Read Events? John Weller 01380 723235 07976 393631 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Ted Roche > Sent: 05 January 2007 21:50 > To: [EMAIL PROTECTED] > Subject: Re: FW: Error Handling > > > On 1/5/07, John Weller <[EMAIL PROTECTED]> wrote: > > > > I have an app which runs at intervals unattended overnight. It > is triggered > > by Windows Scheduler. The error handler enters details of any > error into a > > log and then shuts the app down by issuing a CLEAR EVENTS > command which I > > understand to immediately return to the line following the READ > EVENTS line > > where I have my shutdown routine. > > I'm curious. If you are running an unattended app, why are you > invoking an event handler? > > -- > Ted Roche > Ted Roche & Associates, LLC > http://www.tedroche.com > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
