Hi,
In our ASP application, we are using a visual basic Dll file to perform database operations. We have a function in our Dll file for executing stored procedures.
This function takes 3 input parameters from ASP
1. Connection String
2. SQL String (call stored procedure string)
3. Input Parameters.
We are using “Microsoft ODBC for Oracle” drivers for the database connectivity .Due to some crash problems; we have changed the drivers to “Oracle 10g Drivers”. After changing this none of the procs seem to work
Sample SQL String -> “{call Package.Stored_ Proc(? , {resultset 100, v_flag })}"
? is for the input parameter which we will add using ADODB.Command object
V_Flag is the output parameter which we directly specify in the call proc statement.
When we are using “Microsoft ODBC for Oracle” drivers, it is working fine. But when we are changing the drivers to “Oracle 10G”, it is throwing error “V_Flag : Invalid Identifier” and the proc is not getting executed.
Is anyone aware of this problem/work around?
In our ASP application, we are using a visual basic Dll file to perform database operations. We have a function in our Dll file for executing stored procedures.
This function takes 3 input parameters from ASP
1. Connection String
2. SQL String (call stored procedure string)
3. Input Parameters.
We are using “Microsoft ODBC for Oracle” drivers for the database connectivity .Due to some crash problems; we have changed the drivers to “Oracle 10g Drivers”. After changing this none of the procs seem to work
Sample SQL String -> “{call Package.Stored_ Proc(? , {resultset 100, v_flag })}"
? is for the input parameter which we will add using ADODB.Command object
V_Flag is the output parameter which we directly specify in the call proc statement.
When we are using “Microsoft ODBC for Oracle” drivers, it is working fine. But when we are changing the drivers to “Oracle 10G”, it is throwing error “V_Flag : Invalid Identifier” and the proc is not getting executed.
Is anyone aware of this problem/work around?
Comment