As long as your servers are returning the exceptions back to the client, you
shouldn't need to do anything fancy. If you have an exception handler in a
server process, you won't see the exception in the client unless you raise
it again.
----- Original Message -----
From: Tom Munro Glass <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Sent: Tuesday, December 21, 1999 4:06 AM
Subject: [DUG]: Threads and COM
> Can someone please give me some tips for exception handling in a COM-based
> application?
>
> The application uses a number of in-process and out-of-process COM
servers,
> and exceptions are occurring but the Application.OnException event is not
> getting called. The result is that the application displays an error
message
> and then terminates without me having a chance of dealing with the source
of
> the exception.
>
> I see that the application has several threads (I'm not creating any
threads
> directly), so I assume that these are being created by COM. I suspect that
> the exceptions are occurring in one of these threads, but how do I go
about
> catching these?
>
> ==================================================================
>
> Tom Munro Glass
>
> +----------------------------------------------------------------+
> | E-mail: |
> | Internet: [EMAIL PROTECTED] |
> | Web sites: |
> | TMG CONSULTANCY: http://www.tmgcon.com |
> | Tewkesbury Web: http://www.tmgcon.com/tewksweb |
> +----------------------------------------------------------------+
>
> --------------------------------------------------------------------------
-
> 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
