How do you resume next?

[kayos592]

CREATE TABLE TestTable (Field1 INT) GO DECLARE @Err INT INSERT INTO TestTable (field1) VALUES (9999999999) SELECT @Err = @@Error IF @Err <> 0 BEGIN PRINT 'Im In' INSERT INTO TestTable (field1) VALUES ('1235456') END SELECT * FROM TestTable WHERE field1 = 'ABC' SELECT @Err = @@Error IF @Err <> 0 BEGIN PRINT 'Im In' INSERT INTO TestTable (field1) VALUES ('1235456') END When executing the above code, you will enter the first @Err condition but not the second. Both errors produce the same Severity level so I'm not sure why it resumes on one but not the other. Is there any way to force an SP to resume next?

-Kay

[Colin Angus Mackay]

kayos592 wrote:

When executing the above code, you will enter the first @Err condition but not the second.

I don't see where the second condition, a simple SELECT, could fail under normal conditions. It could return an empty result set, but that's about it. What error are you expecting?

kayos592 wrote:

Both errors produce the same Severity level so I'm not sure why it resumes on one but not the other.

I don't see what error the second condition is producing. And I don't know what you mean by "it resumes on one but not the other".

---

Upcoming events: * Glasgow: Introduction to AJAX (2nd May), SQL Server 2005 - XML and XML Query Plans, Mock Objects, SQL Server Reporting Services... Never write for other people. Write for yourself, because you have a passion for it. -- Marc Clifton My website

[kayos592]

If you execute the attached code in SQL Query analyzer you will see what I'm talking about. Basically, if you try a simple select on an INT field where the where condition is looking for Alpha characters it will give you an error. Simply put, the below code is a simple select which causes an error. Now I know I can check values prior to everything but I want it to continue onto the next record in the event that a simple select causes an error instead of just dying. Please let me know if I should elaborate... CREATE TABLE TestTable (Field1 INT) GO DECLARE @Err INT SELECT * FROM TestTable WHERE field1 = 'ABC' SELECT @Err = @@Error IF @Err <> 0 BEGIN PRINT 'Im In Error Handling number 2' END Now what I mean by "it resumes on one but not the other" is for the first error it will go into the error condition and even execute more of the script, however on the simple select error, it will stop right there and progress no further. Hope that clarifies...

-Kay