Roger Upole wrote:
I've run into this somewhere before. It turns out that the output
parms are
actually returned as an extra recordset, so you need to call
NextRecordset
before trying to access them.
From digging into the source, if you add
rs.NextRecordset() at line 741 of adodbapi.py, the
Vernon,
I have now also tested this with SQL Server Express 2005 on vista and am
still getting an error.
I am adding my previous email to you here for the benefit of the list:
On both XP and Vista, I am using 2.2.5. I don't see a 2.2.6 on
sourceforge.
As for the SQL Server versi
Randy:
Just to make sure...
what version of adodbapi are we talking about?
>>> import adodbapi
>>> adodbapi.version
'adodbapi v2.2.6 '
>>>
--
Vernon
On Tue, May 26, 2009 at 1:16 PM, Randy Syring wrote:
> Vernon,
>
> I didn't mention this in my last email, but I also tried the:
>
> SETÂ @param =
Randy:
I am no longer employed by the company who supplied the SQL server I
used to test on, and am stuck with SQLexpress on my laptop. No Query
Analyzer. (Bah!) Clearly, either my test was invalid, or there is a
difference in SQL versions. What version are you using?
--
Vernon
On Tue, May 26, 20
Vernon Cole wrote:
In this case, the proceedure outputs TWO record sets, since there are
two SELECT statements.
If the second select statement, "select @param = 10" were changed to
"SET @param = 10" then, I believe, the result
would have been as expected.
Vernon, thanks for your comments.
According to PEP 249...
.callproc(procname[,parameters])
Call a stored database procedure with the given name. The
sequence of parameters must contain one entry for each
argument that the procedure expects. The result of the
call is returned a
I found this post:
http://bytes.com/groups/python/38259-sql-server-stored-prcedures-output-parameters
which was helpful in getting me started. However, that method does not
yield the output parameters if a recordset is output in the SP. So, if
my SP is:
CREATE PROCEDURE sp_test_only_out
