>Hi Bob,
>
>-------------
>Can't you just send a batch like:
>
>UPDATE whatever....
>SELECT @@error errnum, @@rowcount rowcount
>
>Which would return a cursor that contained the info?
>--------------
>
>Yes for @@rowcount without triggers,
>No for @@error because any error on UPDATE, kill the SQL batch,
>and the SELECT is not executed.
>
>Fabio

Well, if it is a fatal error, even in an SP, the batch will stop anyway.

As far as rowcount, that's true, forgot about triggers affecting that.

In this case, SQLExec will return a failure code and you can use aerror() to get the SQL error info.

BOb