FreeTDS Development Group

["Rogers, Tom" <tom.rogers AT ccur.com>]

Up until about a month ago, we were told by several on this group that
FreeTDS would not support output parameters on MS SQL because of a change
Microsoft made in the way it handled output params, circa SQL 7.0, SPx.  At
that time, they changed the output params such that they were being sent
"out of band" and not part of the normal messages returned (or something
like that).

We were using build 6.2, with UnixODBC on Linux, connecting to MS SQL 7.0.
And calling via the escape clause format of UnixODBC:

query = "{? = call mysp(?, ?, ?}"

Than, binding input/output, and input and output params via ODBC's
SQLBindParameter.

The SP would work, but output parameters would not be populated.  We were
told by several, including you Frediano, if memory serves, that in order to
get this to work, some internals would have to change related to the use of
rpc, and that it was work in the queue.

That is the last I heard.

Thomas Rogers
System Engineer
Concurrent Computer Corporation
> phone: 215.712.7422 x7261


-----Original Message-----
From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT vodafone.com]
Sent: Tuesday, July 01, 2003 8:37 AM
To: FreeTDS Development Group
Subject: RE: [freetds] Using sp_executesql with Microsoft SQL Server
2000


> 
> Recently we had issues with the current FreeTDS 
> implementation working with UnixODBC in that we were not 
> getting stored procedure output parameters returned.  The 
> issues surrounding output parameters and TDS and how 
> Microsoft changed things around SQL 7.0 timeframe are pretty 
> well documented in the archive so I won't digress.
> 

Can you explain deeply your problems ??
How you call a stored procedure?
Output parameters should work in all library...

freddy77
_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds