As somebody who has worked on VB apps that use OnError..ResumeNext
around the entire code, I would have to say that it is a pretty bad
idea.
You really want to know where the error occurred and why - I only put
exception handlers around very small pieces of code such as '.POST' and
look for say key violations.
Grant Black
Software Developer
SmartMove (NZ) Ltd
Phone: +64 9 361-0219 extn 719
Fax : +64 9 361-0211
Email: [EMAIL PROTECTED]
> -----Original Message-----
> From: Tony Sinclair [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 19, 1999 12:13 PM
> To: Multiple recipients of list delphi
> Subject: [DUG]: Error message reporting
>
>
> Hi all,
>
> I am wondering how I would go about setting up somthing like
> I have done
> before in VB which is a generic error message handler
>
> ------------------
>
> FindFirstTabExit:
> Exit Function
>
> FindFirstTabError:
> HandleError "findFirstTab", Error$, Err
> Resume FindFirstTabExit
>
> ------------------
>
> where HandleError is a procedure that either spits out a
> message box or
> data to a log file or dataset. Error$ is the error message
> returned by
> the application and Err is the error number. The string const is just
> the name of the function or procedure. Do I have to capture
> and specify
> for each error type eg On EDatabaseError do begin? or do I need to
> create my own decendant from TExceptionEvent?
>
> Thanks in adavnce
>
> Tony
>
> --
>
>
> Tony Sinclair
> Holliday Group Limited
> Christchurch
> New Zealand
>
> "I like deadlines. I especially like the
> sound they make as they go wizzing by."
>
>
> --------------------------------------------------------------
> -------------
> New Zealand Delphi Users group - Delphi List -
> [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
