SQL Server stored prcedures with output parameters

[Aahz]

In article <HHWmd.10924$nj.1324 at lakeread01>,
Steve Holden  <steve at holdenweb.com> wrote:
>
>Has anyone, with any driver whatsoever, managed to retrieve output 
>parameters from a SQL Server stored procedure? I've just been rather 
>embarrassed to find out it's not as easy as it might seem, and people 
>are saying bad things about Python as a result :-(
>
>mx.ODBC, which I regard as a highly-capable module, does not support
>the callproc() API, and suggests use of the ODBC call format. It has
>caveats in (some of) the documentation implying that output parameters
>cannot be handled due to their indeterminate memory requirements,
>however.

Keep in mind that it's been several years since I used Python with SQL
Server and about all I remember is that we used stored procedures
heavily with no problems.  I have no clue whether we tried using stored
procedures with output parameters, but I wonder why you can't just use a
SELECT to call the stored procedure and return the values.  Or at least
right another stored proc that does something roughly similar.
-- 
Aahz (aahz at pythoncraft.com)           <*>         http://www.pythoncraft.com/

WiFi is the SCSI of the 21st Century -- there are fundamental technical
reasons for sacrificing a goat.  (with no apologies to John Woods)