>Hi Charles,
>
>In T-SQL RETURN is expected to return a status with 0 indicating succsess. The value can be returned through an OUTPUT parameter. This way you can do all the error checking in the stored procedure and return appropriate status code. In the calling stored procedure you'll than check that status code to determine success or failure.
>
>BTW, The RAISERROR format you're using is not documented. I was surprised that it works. Where did you find it?
>FYI, the error codes over 50,000 are reserved for used defined messages.
>

RAISERROR eCode eMessage
it is reasonable and profit, but it is not possible to insert ( severity, state ...)

But also in SQL Server they have succeeded in complicating some very simple things.

-- default error
RAISERROR (14003,16,1)
-- I can redefine it !!
RAISERROR 14003 'This is not a error!'
-- But i cannot redefine error under 13!!!!000
RAISERROR 11000 'This is not a error!'

Also this time the number 13 have struck!
As in the skyscrapers we have to remove 13 from the CPUs.
:)