Re: Oracle 9.2 OLEDB and NVARCHAR2

• Previous message: Christopher D: "vfpoledb driver v8 sp1 - poor performance"
• In reply to: Mike Johnston: "Oracle 9.2 OLEDB and NVARCHAR2"
• Messages sorted by: [ date ] [ thread ]

Date: Tue, 4 May 2004 16:10:42 -0400

To follow up:
It seems that Oracle wants to see the obvalue in the bindings to have a
value for an output parameter. This seems to be controlling what Oracle
thinks the length is and not the cbLen or the "paramsize" on the bindings
structure.

When I set this to the length, I can assign exactly up to that number of
characters to the string in the SP.

"Mike Johnston" <mike@yahoo.com> wrote in message
news:uGyLdEeMEHA.2500@TK2MSFTNGP12.phx.gbl...
> Hi,
> I am calling a stored procedure with an OUT parameter of NVARCHAR2. I
have
> set the property NVarChar for the command as documented.
>
> When I call my SP, i can set these OUT parameters to null with no issue.
I
> can also assign OUT parameters that are integers in the SP that get
returned
> correctly. It's only when I assign a non-null value to the NVARCHAR2 OUT
> parameters i have the issue. I am using C++ and calling the OLEDB function
> directly. This same code works perfectly with the SQL Server OLEDB
provider
> (not that this means much :-)
>
> If I write another SP that calls this SP with OUT NVARCHAR2 parameters
this
> works as expected. It must be something in the binding I'm guessing.
>
> Thanks in advance
>
>

• Previous message: Christopher D: "vfpoledb driver v8 sp1 - poor performance"
• In reply to: Mike Johnston: "Oracle 9.2 OLEDB and NVARCHAR2"
• Messages sorted by: [ date ] [ thread ]