Should be able to get the program (or method in a class) and line number from the error. Might be an idea to look at try catch as well for special problems. I only really started using that after trying it in c# Allen
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sytze de Boer Sent: 29 September 2008 14:41 To: [EMAIL PROTECTED] Subject: Re: Numeric overflow I didn't explain myself terribly well. On reflection, I think I've found the answer. My error routine logs the LINENO() reference. I had completely forgotten about this. I've now tested this and I can tell exactly what line of code contains the error Well, in my development system anyway. Now to test it with a live exe system ...................... SdB _______________________________________________ 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 Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** 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.
