How do I trap a level 16 error caused by an opequery query through to an Oracle Database that is executed using sp_executesql. This error occurs at the beginning of a failrly long stored procedure and kills execution before I can even check @@error
Some errors in SQLServer are Untrappable in T-SQL. You can trap it in application code (ADO for example) but since you refer to @@Error it seems like you are are trying to use T-SQL.
Write a rude letter to Microsoft. I have.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply