FreeTDS Development Group

["Paul Wehlage" <paul.wehlage AT gd-is.com>]

You have correctly summarized my problem.  The table
is correct (I made it permenant and ran queries against
it with the query analyzer).  I had administrator (sa)
rights for the account I was using.

I can manually create the procedure.  If I run the procedure
using parameters it does not work.  If I "plug in" the parameters
I get the correct results.  "Plugging in" all but one
parameters gives me zero rows affected (no matches).
It has to be something related to parameter processing
as you suggested below.

-----Original Message-----
From: bounce-freetds-131749 AT franklin.oit.unc.edu
[mailto:bounce-freetds-131749 AT franklin.oit.unc.edu]
Sent: Thursday, June 07, 2001 11:26 AM
To: TDS Development Group
Subject: [freetds] Re: Request for information about
DatabaseMetaData.getTables


> I have looked at the problem quite a bit and determined that
> I do not get the same results from the stored procedure that
> gets executed as I get by just building the equivalent SQL string
> without using prepared statement parameters.

So, you're saying that the temporary table being built has the
correct values in it, but that the final select out of the
temporary table is not working when the query is executed
through a stored procedure?

> create proc #jdbc#3(@P1 nvarchar(4000), @P2 nvarchar(4000), @P3
> nvarchar(4000), @P4 nvarchar(4000)) as select TABLE_CAT=cat,

One obvious difference between this and the direct query is
the stored procedure's use of Unicode.  If you manually create
the procedure using non-Unicode parameters, does it work then?

What kinds of rights do you have when trying this?

--
Curt Hagenlocher
curt AT hagenlocher.org

---
You are currently subscribed to freetds as: [paul.wehlage AT gd-is.com]
To unsubscribe, forward this message to
$subst('Email.Unsub')