Raise an error to ADO from a stored proc

Question

Post reply

Raise an error to ADO from a stored proc

Viewing 4 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Farrell Keough SSCoach Points: 17414 More actions · Answer 1

I am a bit lost on this statement:

--add rabies tag service

EXEC @return = AddService @animalID=@animalID, @serviceID=@serviceID

Might you want to be using

--add rabies tag service

SELECT @return = AddService, @animalID=@animalID, @serviceID=@serviceID

FROM SomeTable

WHERE SomeCondition

I wasn't born stupid - I had to study.

Adam O'Neil SSC Veteran Points: 298 More actions · Answer 2

>>UNLESS I cause the error is not related to the nested proc call.<<

What am I saying here?

After much Googling, I found that I needed to use adExecuteNoRecords with my Connection.Execute method call. There were some other conditions mentioned in this article that I didn't find to be true, and I'm not sure I fully grasp what's at work here, but I'm happy I got my thing to work...

Adam O'Neil SSC Veteran Points: 298 More actions · Answer 3

>>

I am a bit lost on this statement:

--add rabies tag service

EXEC @return = AddService @animalID=@animalID, @serviceID=@serviceID

<<

Thanks for replying. The statement above is meant to branch to another stored proc and return the result. It so happens that the param names of the nested proc are named the same as the params being passed to them. Hence the redundant-looking param/value pairs. It's not meant to be a SELECT statement.

rschaeferhig SSCrazy Eights Points: 8776 More actions · Answer 4

Note for next time: Post the calling VBScript as well. If I had seen your Connection.Execute statement I could have told you it was missing the adExecuteNoRecords. It didn't even occur to me to ask since I always code adExecuteNoRecords for any Stored Procedure that isn't returning a recordset...