Hi,
We are attempting to execute a Stored Procedure with both IN and OUT params.
We have found that the IN param immediately before the first OUT param is being corrupted. It seems to be having a '?' to the end of the paramValue.
Has anybody else seen this, and is there a workaround other than to add an extra IN param that isnt used?
Thanks,
Keith...
Corruption of input params
Re: Corruption of input params
Please send to our support email address a detailed description of the problem,
text of your stored procedure and a code sample to reproduce the problem.
text of your stored procedure and a code sample to reproduce the problem.
Corruption of input params
OK,
I've sent the details to the support group a day or so ago, but have not heard anything back.
Have you been able to replicate this problem?
I've sent the details to the support group a day or so ago, but have not heard anything back.
Have you been able to replicate this problem?
Re: Corruption of input params
We sent you our reply by email.