🚀 go-pugleaf

I'm using BCB 6.0 enterprise with TADOQuery to talk to a SQL Server
database. I have added constraints on my tables to not allow duplicate
entries into some of the tables. I have added a try ... exception clause
around the update to trap the error, but I'm not getting the exception.
Instead there is a message box from the inside the borland code with a
fairly ugly message  --

"Project CritLabel.exe raised exception class EOleException with message
"Violation of UNIQUE KEY constraint "IX_Reflectors'. Canot insert
duplicate key in object "Reflectors". Process stopped. Use Step or Run
to continue."

and it bounces me out of the save routine. I would prefer to trap the
error myself, put out a more meaningful message and roll back the update
in a more controlled manner. Do I have to set some sort of a flag or
include some special code for the compiler to handle exceptions?

The code I've used to test:
    try {
          RQuery->UpdateBatch(arAll);
     } catch (Exception &e ) {
          ShowMessage( "Exception found - "+e.message);
          CSDatabase->RollbackTrans();
          return;
      }