ODBC failure with plsql

Question

I have Oracle9i Client 9.0.1.1.1 and Oracle ODBC Driver 9.1.0.1 installed. When I connect to the remote database with the ADODB activex object with this driver, I get different results running the ADODB.execute command on a plsql procedure depending on the version of the database I am connecting to.
If I am connecting to an Oracle9i 9.2.0.1.0 database, the plsql executes successfully. If I am connecting to an Oracle8i 8.1.7.2.0 database, the plsql fails.
Running the ODBC trace gives two different syntaxes for the different calls also.
Oracle9i 9.2.0.1.0 shows:
Processid:{3D14 714-7d8     ENTER SQLExecDirectW
          HSTMT 00A54850
          WCHAR * 0x024D0E50 [     131] "{ call intp.bline_str_create.createStr(2003, 'VCO', 'W', 'C108010102', 'test', 'C.1.08.01.01.02.CC', 'OE', '062690', '', '', 'F') }"
          SDWORD 131
Processid:{3D14 714-7d8     EXIT SQLExecDirectW with return code 0 (SQL_SUCCESS)
          HSTMT 00A54850
          WCHAR * 0x024D0E50 [     131] "{ call intp.bline_str_create.createStr(2003, 'VCO', 'W', 'C108010102', 'test', 'C.1.08.01.01.02.CC', 'OE', '062690', '', '', 'F') }"
          SDWORD 131
while Oracle8i 8.1.7.2.0 shows:
Processid:{3D14 714-7d8     ENTER SQLExecDirectW
          HSTMT 00A54CD8
          WCHAR * 0x024D8728 [     114] "idaho.ifpapk_manage_task.add_task('COS', 568, 'C.1.08.01.01.02.A1', 'test', 'test', '09/30/2002', '01/01/4712', 0)"
          SDWORD 114
Processid:{3D14 714-7d8     EXIT SQLExecDirectW with return code -1 (SQL_ERROR)
          HSTMT 00A54CD8
          WCHAR * 0x024D8728 [     114] "idaho.ifpapk_manage_task.add_task('COS', 568, 'C.1.08.01.01.02.A1', 'test', 'test', '09/30/2002', '01/01/4712', 0)"
          SDWORD 114
          DIAG [37000] [Oracle][ODBC][Ora]ORA-00900: invalid SQL statement
(900)
Please help.

Answer 1

My mistake on the ODBC Driver Verion number - Sorry. I was using the Oracle ODBC Driver version 9.0.1.0.1. We upgraded to the 9.0.1.5 Oracle ODBC driver with no success.
The Oracle 8.1.7.2 database I am connecting to in the failed instance is not willing, at this time, to upgrade. It is in their plans for the future which doesn't help me.
The syntax for the failing call to the PLSQL is:
opConn.ConnectionTimeout = 60;
     opConn.CommandTimeout = 60;
     opConn.Open(Session("OP_ConnectionString"),
Session("OP_User"),
Session("OP_Password"),
     strQuery2 = "idaho.ifpapk_manage_task.add_task('"
                    + usernameU + "', " + proj_id + ", '"
                    + tt_number + "', '" + tt_name + "', '"
                    + tt_description + "', '"
                    + tt_start_date + "', '"
                    + tt_completion_date + "', "
+ cn_parent_task_id + ")";
opConn.Execute(strQuery2);
I know the connection is getting made - I can perform a Select statement successfully.
Thanks.