Oracle OLE DB and command Parameters in VB6

Question

Hi,
here's my problem :
When i a VB6 command object ( ado ) this works fine with Oracle client 8i/9i, but with 10g it seems to truncate all my string parameters
Here is my vb code :
Public Function PRC_APPLICATIONSCENARIO _
ByRef p_vConnection As Variant, _
ByVal p_sZlCle As String, _
ByVal p_dDateDeb As Date, _
ByVal p_iDiffdate As Integer, _
ByRef p_sCodeErr As String, _
ByRef p_sErrMsg As String, _
ByRef p_lScenar As Long, _
ByRef p_lSoc As Long _
) As Long
On Error GoTo Err
Dim cmd As ADODB.Command
Dim param As ADODB.Parameter
Set cmd = New ADODB.Command
cmd.ActiveConnection = p_vConnection
Set param = cmd.CreateParameter("iZlCle", adInteger, adParamInput, , CLng(p_sZlCle))
cmd.Parameters.Append param
Set param = cmd.CreateParameter("dDateDeb", adBSTR, adParamInput, , Format(p_dDateDeb, "dd/mm/yyyy"))
cmd.Parameters.Append param
Set param = cmd.CreateParameter("iDiffDate", adInteger, adParamInput, , CLng(p_iDiffdate))
cmd.Parameters.Append param
Set param = cmd.CreateParameter("nCodeErr", adInteger, adParamOutput)
cmd.Parameters.Append param
Set param = cmd.CreateParameter("vErrMsg", adBSTR, adParamOutput, 200, String(200, " "))
cmd.Parameters.Append param
Set param = cmd.CreateParameter("lIdScenar", adInteger, adParamInput, , CLng(p_lScenar))
cmd.Parameters.Append param
Set param = cmd.CreateParameter("lIdSoc", adInteger, adParamInput, , CLng(p_lSoc))
cmd.Parameters.Append param
cmd.CommandText = "{CALL ApplicationScenario" & _
cmd.Execute
this is what i have with 8i ( checking with SQL Monitor ) :
BEGIN ApplicationScenario(:1,:2,:3,:4,:5,:6,:7); END;
:1 = 1
:2 = '01/11/2010'
:3 = 6
:4 = 0
:5 = <NULL>
:6 = 2602
:7 = 1
and this is what i have in 10g :
BEGIN ApplicationScenario(:1,:2,:3,:4,:5,:6,:7); END;
:1 = 1
:2 = '0'
:3 = 6
:4 = 0
:5 = <NULL>
:6 = 2602
:7 = 1
If someone could help me find where i' m wrong, or maybe it's a known bug ?

Answer 1

Hi,
assuming you called the function from a sql select statement (select gf_test from dual;) then the error is as expected, you can't do DML inside a select. Parallel DML is unlikely to be your problem.
I'm a little unclear what you are trying to do with this function though, you could hack it by declaring this an autonomous transaction, but it's unlikely that that is the best way to solve the business problem. If you are trying to find the value of a primary key that is generated from a sequence then the normal way of doing this is to have a before insert trigger that generates the pk for you and then have a pl/sql procedure to do the insert and return the pk to the calling application (which can be powerbuilder or any other language that can call pl/sql.
Niall
Bill Mac wrote:
OK I have managed to get some code to return an error number and this is it:
ORA-14551: cannot perform a DML operation inside a query
Cause: DML operation like insert, update, delete or select-for-update cannot be performed inside a query or under a PDML slave.
Action: Ensure that the offending DML operation is not performed or use an autonomous transaction to perform the DML operation within the query or PDML slave.
The code was:
create or replace function GF_TEST return NUMBER is
retval number;
begin
SET TRANSACTION READ WRITE;
UPDATE parameters
SET last_parent_co = last_parent_co + 1
WHERE (row_no = 1)
RETURNING last_parent_co INTO retval;
COMMIT WORK;
retval := 1001;
return retval;
exception when others then
return sqlcode;
end;
Does that now make any sense to any one? Am I a pdml slave?
Edited by: Bill Mac on 07-Apr-2009 07:38