🚀 go-pugleaf

���������� ������,

Thank you very much for your fast and helpful answer. While I waited for an
answer I made a comprehensive lookup in the Microsoft Data Access Components
SDK help at MSDN web site and I was wonder how UNintuitive is decided to put
all errors in the Connection..., but it will work.

Thank you again.

Emil.

"Victor Cazacov" <victor@kazakov.net> wrote in message
news:3e240752@newsgroups.borland.com...
> ������, Emil !
>
>  ED> s.o., but there is no property available for the SQL error code
>  ED> returned by the SQL Server.
>
> TADOConnection::Errors
>
> look at code of my database errors handler:
>
> if ( ADOConnection->Errors->Count )
> {
>     ReportStr+= "Errors Collection:\n";
>     for (i = 0; i < ADOConnection->Errors->Count; i++)
>    {
>       ReportStr+= AnsiString("  Source: ")+
>         ADOConnection->Errors->Item[i]->Source+"\n";
>       ReportStr+= AnsiString("  Native error code: ")+
>         ADOConnection->Errors->Item[i]->NativeError+"  ";
>       ReportStr+= AnsiString("Error number: ")+
>         ADOConnection->Errors->Item[i]->Number+"\n";
>      }
>
> }
>
> --
> Victor
>
>