I've got a procedure which after encountering error 547
does a RAISERROR with a detailed error message.
This works fine, if there is no procedure called between
trapping the error 547 and the RAISERROR statement. But as
soon as you call a procedure (in this case a procedure to
create the error message) before the RAISERROR statement
the error cannot be detected by ADO (only the errors which
SQL SERVER itself produces).
However when calling the procedure from the SQL Query
yzer all the errors from the error stack (also the one
from the RAISERROR statement) can be seen.