views:

37

answers:

2
A: 

Does your stored procedure start with SET NOCOUNT ON? The lack of this can sometimes cause issues if the stored procedure is processing multiple queries before the final SELECT.

CodeByMoonlight
Yep.. Got NOCOUNT set to ON
Mike
+1  A: 

Got it.. if you take a look at my parameters up top I am accidentally assigning transaction to customer and customer to transaction. DOH!

Thanks, Mike

Mike
<hehe> it's often these really silly little things......
marc_s