RE: [dbi] YA Stored Procedure Question

I don't use ADO but I do use ODBC. SQL Server normally batches the statements in a procedure so in ODBC terms for your procedure you have to: execute fetchall SQLMoreResults # moves to the update rowcount - to get row update count SQLMoreResults - # moves to the second select fetchall

Re:[dbi] YA Stored Procedure Question

Thanks for the feedback everyone. I need to add that I tried another test. In this one, I pulled out the insert and update statement from the SP (just to confirm that what I wanted to do really would work) and the result set was returned and the fetchrow_array call did succeed and returned my

RE: [dbi] YA Stored Procedure Question

From: Martin J. Evans [EMAIL PROTECTED] I don't use ADO but I do use ODBC. SQL Server normally batches the statements in a procedure so in ODBC terms for your procedure you have to: execute fetchall SQLMoreResults # moves to the update rowcount - to get row update count SQLMoreResults -

RE: [dbi] YA Stored Procedure Question

On Mar 2, Jenda Krynicky scribed: Try to add SET NOCOUNT ON on top of the stored procedure. That should prevent the select into and update statements from getting in the way. Thanks! That's it. I forgot about that. Dave