🚀 go-pugleaf

Ciao Giuliano,
It seems to be an Italian discussion, shouldn't we speak italian? ;-D
I had your same problem but different exception : in my apps I use to wrap
the ExecSQL() method in a function :
bool __fastcall ExecSQL(TADOQuery *query)
so I can execute the query and handle the exception returning false if exec
wasn't right.
I do your same catch block but with EADOError instead of EOleException, and
never got the EADOError fired, every time it is the catch(Exception &e) to
be executed.
I should think that they use different type of exception, or they use
directly Exception type.
I advice you to look ad the sources, to see if you can see how the exception
is thrown, I'll look at them too, but now I have no time to do it, so if
I'll find out sth, I'll let you know.

Ciao
    Formentz

> I would like to read some comments from anyone that has had a problem
> like this, in order to understand if it's a real bug, so that I can report
> this to Borland.
>
> Thanks.
>
> Giuliano