I tried to post this earlier but my ISP was having problems and I suspect it fell into a black hole. I've not seen it nor any responses. If it has appeared before and generated any response please accept my apologies for not seeing them or replying.
John Weller 01380 723235 07976 393631 -----Original Message----- From: John Weller [mailto:[EMAIL PROTECTED] Sent: 05 January 2007 13:05 To: [email protected] Subject: Error Handling 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 have had an error in an SQL statement which is inside a scan which is in turn inside a FOR ENDFOR loop in a form method called by another method on the same form and I am not getting the behaviour I expect. It tries to execute the SQL statement, executes the error handling code, makes an entry into the log then appears to return to the FOR ENDFOR loop and executes the SQL statement again thus triggering the error routine again - and so on.... There is a log entry for every time the error occurs in the loop. I have tried tracing the code but keep getting the dreaded 'Source Not Available' when it gets to the error handling routine which is in a separate program (but still in the project). Any suggestions gratefully received. John Weller 01380 723235 07976 393631 _______________________________________________ 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.
