[freetds] SP Syntax error using freeTDS and UnixODBC on Linux

Rogers, Tom tom.rogers at ccur.com
Wed May 7 23:11:52 EDT 2003

Downloaded v 0.61 and built with tdsver=7.0 option (from memory, sorry).

And, the whitespace I was using was something like:

  "{ ? = call myproc( ?, ?, ?, ? ) }"

Thanks.  I will try with NO whitespace and see what I get.

Tom Rogers

-----Original Message-----
From: James K. Lowden
To: FreeTDS Development Group
Sent: 5/7/03 10:02 PM
Subject: Re: [freetds] SP Syntax error using freeTDS and UnixODBC on Linux

On Wed, 7 May 2003 16:17:20 -0400 , "Rogers, Tom" <tom.rogers at ccur.com>
> On my Linux machine with UnixODBC 2.2.3-1 using freeTDS 7.0 into a MS
> SQL 7.0 server I have a simple, sample app that calls a stored
> using SQLBindParameter and SQLExecDirect.  The SQL server returns a
> syntax error if using escape clause syntax, "{ ? = call myproc(?, ?,
> }".  I say this is on "my machine", as a colleagues machine the
> SQLExecDirect call runs fine, except no output params or return code.
> I am supposed to debug the no RC/Output params problem, but it is
> difficult as I can't get the SP to work in the first place.  I can
> execute the SP if I use the regular t-sql equiv:  "execute myproc
> val1, val2".  That works fine.  
> Oh, on my colleagues machine I have tried SQLMoreResults to fetch any
> recs/diag recs, etc.  That seemed to get the ReturnCode to show up but
> not the output param.
> I have searched the various mailing lists, news groups high and low
> triple checked my config.
> What should I do?

There were, perhaps still are, whitespace problems with that syntax,
recently fixed.  See ChangeLog in CVS and the ML archives for
You could post your TDSDUMP log here, taking care with the passwords. 
You don't mention what version of FreeTDS you're using.  Frediano will
be able to tell you if you can work around the problem by eliminating
some whitespace.  


FreeTDS mailing list
FreeTDS at lists.ibiblio.org

More information about the FreeTDS mailing list