🚀 go-pugleaf

Hmmm

I generally use

System::CheckSafecallResult(hr)

where hr is the HRESULT value returned from ADO COM objects
method calls...

I think it throws EOleException when it detects an error. There is some
extra data you can use written in the thrown exception object.

You can also read the connections error collection directly... I do it
when I debug... To learn how lookup ADODB.Recordset, ADODB.Connection
and that familly of objects on the MSDN... also check out the
Adoint.hpp header file that comes with Builder to see exactly which
methods _di_Errors and _di_Error objects have... be warned that most
of their parameters are OleVariants which are a PAIN!!! to work with in
Builder... as there are not enough accessible operators and methods defined
on it... (for example it doesn't even have a == operator defined on it!!!!!
Yuck!)
One way to get data out from it is to cast it to VARIANT structure and
read it by manually... (make some helper functions and you get used to it
soon...)


HTH,
    Jurko

<jqpdev> wrote in message news:3b9d86b7_1@dnews...
> Hello everyone,
>
> I'm looking for info. on how to handle ADO errors and what are the
exception
> classes.  The C++ Builder on line help didn't help much.  I found
something in
> the help for the ADOConnection component.  It has a _di_errors property
but
> there isn't much on it.  I'm sure Borland has provided a way to use C++
> exception handling constructs, but I don't know the names or the structure
of
> the exception classes.
>
> I also found the EADOError in the online help but again there isn't much
written
> on it, and it doesn't contain much info.
>
> TIA
>
>
>