Stored Proecure statement precedence
Posted on 2003-11-21
Sometimes when im creating a stored procedure that needs to a) update or insert, b) return data the script which is executed through asp using something like
Set rs = .Execute (within the rest of the SP code)
The script will crash unless i put the select statement before the update or insert statement within the SP. Is there a reason for this, as sometimes this is simply impossible and i end up creating a second sp just to return the data which seems stupid?
Thanks in advance