headers
Rajesh Akolu | 5 Oct 2007 14:36

Not getting return value and output parameter from stored procedure.

 

Hi,

I am using FreeTDS0.65 and unixODBC 2.2.12 on RH Linux 3.4.6. I am connecting to Microsoft SQL Server 2000 from Linux. I am using C++ on Linux.

 

Requirement: To get return value and output parameter after calling a stored procedure.

-------------------

 

I am calling Stored Procedure (SP) with input and output parameter and I am also expecting return value as well.

 

I am calling stored procedure as follows:

 

{? = CALL stp_returnRow(?, ?, ?)}

 

In above case I am expecting both return value and output parameter. The first parameter is input and 2nd and 3rd parameter is output parameter.

 

Please suggest or give us solution

 

Thanks & best regards,

Rajesh Akolu

Project Manager 

Financial Technologies (India) Ltd.         

Board No: 022-26831022     Extn: 254

Fax: 022-26836999

 

rajesh.akolu <at> ftindia.com

www.ftindia.com

Disclaimer:

The information in this E-mail (which includes any files transmitted with it) is CONFIDENTIAL and may be legally PRIVILEGED. It is intended solely for the addressee and access to this email by anyone else is unauthorized. If you have received it in error, please destroy any copies of this message, including any attachments, and delete it from your system notifying the sender immediately. Any disclosure, copying, distribution, dissemination, forwarding, printing or any action taken or omitted to be taken in reliance on it or utilising the same for any purpose other than what it is intended for, is prohibited and may be unlawful.

 

_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com
http://mail.easysoft.com/mailman/listinfo/unixodbc-dev
Permalink | Reply | 1 comment |
headers
Nick Gorham | 5 Oct 2007 14:43
Favicon

Re: Not getting return value and output parameter from stored procedure.

Rajesh Akolu wrote:

>Hi,
>
>I am using FreeTDS0.65 and unixODBC 2.2.12 on RH Linux 3.4.6. I am connecting to Microsoft SQL Server 2000
from Linux. I am using C++ on Linux. 
>
>
>
>Requirement: To get return value and output parameter after calling a stored procedure.
>
>-------------------
>
>
>
>I am calling Stored Procedure (SP) with input and output parameter and I am also expecting return value as
well. 
>
>
>
>I am calling stored procedure as follows:
>
>
>
>{? = CALL stp_returnRow(?, ?, ?)}
>
>
>
>In above case I am expecting both return value and output parameter. The first parameter is input and 2nd
and 3rd parameter is output parameter.
>
>
>
>Please suggest or give us solution
>  
>
None of that is down to the driver manager, I know Easysoft driver will 
do exactly that, so maybe the freetds folk are the ones to ask.

--

-- 
Nick
_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com
http://mail.easysoft.com/mailman/listinfo/unixodbc-dev
Permalink | Reply | 0 comments |
headers
Rajesh Akolu | 17 Oct 2007 12:30

ODBCConfigure returns error while configuring System DSN

 

 

Hi,

I am using FreeTDS0.64 (TDS Version 8.0) and unixODBC 2.2.12 on RH Linux 3.4.6. I am connecting to Microsoft SQL Server 2000 from Linux. I am using C++ on Linux.

 

Problem:  Getting error “Could not construct a property list for (freeTDS)” while configuring ODBCConfig à System DSN.

 

 

Thanks & best regards,

Rajesh Akolu

Financial Technologies (India) Ltd.         

Board No: 022-26831022     Extn: 254

Fax: 022-26836999

 

rajesh.akolu <at> ftindia.com

www.ftindia.com

Disclaimer:

The information in this E-mail (which includes any files transmitted with it) is CONFIDENTIAL and may be legally PRIVILEGED. It is intended solely for the addressee and access to this email by anyone else is unauthorized. If you have received it in error, please destroy any copies of this message, including any attachments, and delete it from your system notifying the sender immediately. Any disclosure, copying, distribution, dissemination, forwarding, printing or any action taken or omitted to be taken in reliance on it or utilising the same for any purpose other than what it is intended for, is prohibited and may be unlawful.

 

_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com
http://mail.easysoft.com/mailman/listinfo/unixodbc-dev
Permalink | Reply | 2 comments |
headers
Nick Gorham | 17 Oct 2007 14:34
Favicon

Re: ODBCConfigure returns error while configuring System DSN

Rajesh Akolu wrote:

> Hi,
>
> I am using FreeTDS0.64 (TDS Version 8.0) and unixODBC 2.2.12 on RH 
> Linux 3.4.6. I am connecting to Microsoft SQL Server 2000 from Linux. 
> I am using C++ on Linux.
>
> Problem: Getting error “Could not construct a property list for 
> (freeTDS)” while configuring ODBCConfig à System DSN.
>

I would guess you haven't got (or setup) a freetds setup lib.

--

-- 
Nick
_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com
http://mail.easysoft.com/mailman/listinfo/unixodbc-dev
Permalink | Reply | 1 comment |
headers
ZIGLIO, Frediano, VF-IT | 17 Oct 2007 14:51

RE: ODBCConfigure returns error while configuringSystem DSN

> 
> Rajesh Akolu wrote:
> 
> > Hi,
> >
> > I am using FreeTDS0.64 (TDS Version 8.0) and unixODBC 2.2.12 on RH 
> > Linux 3.4.6. I am connecting to Microsoft SQL Server 2000 
> from Linux. 
> > I am using C++ on Linux.
> >
> > Problem: Getting error "Could not construct a property list for 
> > (freeTDS)" while configuring ODBCConfig à System DSN.
> >
> 
> I would guess you haven't got (or setup) a freetds setup lib.
> 

If you compiled FreeTDS correctly you should add something like

[FreeTDS]
Description = FreeTDS unixODBC Driver
Driver = /path/to/freetds/lib/libtdsodbc.so.0
Setup = /path/to/freetds/lib/libtdsodbc.so.0

in /etc/odbcinst.ini

and should works out

freddy77
_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com
http://mail.easysoft.com/mailman/listinfo/unixodbc-dev
Permalink | Reply | 0 comments |
headers
Peter Harvey | 30 Oct 2007 21:03

wchar for ini ?

Nick,

Adding wchar support for ini library - stop me if you think its a bad idea.

xxA = 1byte char
xxW = 4byte char = ucs4

Caller can use xx macro which is mapped at build time to xxA or xxW 
functions. The idea is to make the ODBC system information loss-less.

--
Peter

_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com
http://mail.easysoft.com/mailman/listinfo/unixodbc-dev
Permalink | Reply | 2 comments |
headers
Nick Gorham | 30 Oct 2007 22:12
Favicon

Re: wchar for ini ?

Peter Harvey wrote:

> Nick,
>
> Adding wchar support for ini library - stop me if you think its a bad 
> idea.
>
> xxA = 1byte char
> xxW = 4byte char = ucs4
>
> Caller can use xx macro which is mapped at build time to xxA or xxW 
> functions. The idea is to make the ODBC system information loss-less.
>
> -- 
> Peter
>
> _______________________________________________
> unixODBC-dev mailing list
> unixODBC-dev <at> easysoft.com
> http://mail.easysoft.com/mailman/listinfo/unixodbc-dev

Probably a good idea, but then I will get asked for a seperate interface 
for teh ODBC API. I would suggest not using W, that might get confusing 
with SQL...W, maybe xxU, then if I ever gain the energy I could add a 
SQLConnectU and so on.

--

-- 
Nick
_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com
http://mail.easysoft.com/mailman/listinfo/unixodbc-dev
Permalink | Reply | 1 comment |
headers
Peter Harvey | 30 Oct 2007 23:46

Re: wchar for ini ?

Nick Gorham wrote:
> Peter Harvey wrote:
>
>> Nick,
>>
>> Adding wchar support for ini library - stop me if you think its a bad 
>> idea.
>>
>> xxA = 1byte char
>> xxW = 4byte char = ucs4
>>
>> Caller can use xx macro which is mapped at build time to xxA or xxW 
>> functions. The idea is to make the ODBC system information loss-less.
>>
>> -- 
>> Peter
>>
>> _______________________________________________
>> unixODBC-dev mailing list
>> unixODBC-dev <at> easysoft.com
>> http://mail.easysoft.com/mailman/listinfo/unixodbc-dev
>
> Probably a good idea, but then I will get asked for a seperate 
> interface for teh ODBC API. I would suggest not using W, that might 
> get confusing with SQL...W, maybe xxU, then if I ever gain the energy 
> I could add a SQLConnectU and so on.
>
Ok; I will make a pass at it and commit - we can rename some stuff in 
there as you desire :)

--
Peter

_______________________________________________
unixODBC-dev mailing list
unixODBC-dev <at> easysoft.com
http://mail.easysoft.com/mailman/listinfo/unixodbc-dev
Permalink | Reply | 0 comments |

Gmane