Hi
May be I'm missing something, but...
How can I catch an exception raised by an asynchronous function like
TnCnx.Connect in a form. In a TApplication there is a Method for this
(HandleException). Is there something similar for a TForm?
TIA
Veit
--
To unsubscribe or change your
Hi Arno and others!
Some of the heavy work load I experienced a while ago has decreased a bit so
I thought that I should take the opportunity to thank You ALL that tried to
help me.
At the end the solution for me was to use another smtp component. Sorry
about that. (As a request by Francois
Strange logic Henrik,
Even Microsoft's Works doesn't/didn't work with this buggy, API
hooking Embassy Trust Suite pre-installed on newer DELL systems.
Possibly they already fixed it in some service pack? If not,
someone/we should report the bug to either DELL or Wave Systems.
I was hoping that
Hello Veit,
Normally the components handles their own exception by design (as it
should be). Be sure you have no exceptions in events. If there is a
chance that your code can raise an exception then you should have that
event into an try excpet block and handle it.
---
Rgds, Wilfried [TeamICS]
You probably hit the wrong button.
Your mail is addressed to me privately.
Arno
Wilfried Mestdagh wrote:
Hello Veit,
Normally the components handles their own exception by design (as it
should be). Be sure you have no exceptions in events. If there is a
chance that your code can raise an
Arno Garrels wrote:
You probably hit the wrong button.
Your mail is addressed to me privately.
Perfect chaos, sorry. Please ignore this mail.
---
Arno Garrels [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
Arno
Wilfried Mestdagh wrote:
Hello Veit,
Normally the
Hello Arno,
Perfect chaos, sorry. Please ignore this mail.
That's because we are programmers :) However there is one thing. Hitting
'reply to all' does address the mail also to the original poster. I dont
like it as it start often private mailings. And 'reply to all' is a
common used button in
I thought it was figured out that dynamically unloading and reloading the
dll was the problem, which other components probably don't do, and I think
you were given a workaround that worked...to load it manually so that the
loaded count always stays above 0 and it remains loaded.
Dan
Hello Wilfried
Thanks for your reply. The answer is a surprise for me:
Of course I know try except/finally, but why does it work when I
wrap it around TnCnx.Connect? I thought this is an asynchronous
method? But it works. I would have expected that the try/except
block is left right after calling