aldovalerio
Programmer
My application is VB 6.0 using ADO v2.6 against Oracle v8.1.6 with the MS OLE DB provider for Oracle. I've built a data-access layer in a DLL for my ADO code, and I use the same classes in this DLL for other VB applications that use MS SQL Server. In my ADO code, I only use stored procedures (packaged and non-packaged) execute by command objects with
cmd.CommandType = adCmdStoredProc. All this works fine. I'm wondering however, if I can increase performance by using the Oracle provider for OLE DB, BUT I don't want to change my ADO code just for that. Can I use the Oracle provider for OLE DB without having to use the ODBC call syntax? I've tried chaning my connect string to the Oracle provider but I get error messages saying that I have the wrong number of parameters for my stored procedures. I've seen this on a few Web sites as an example of ADO code with the Oracle provider:
' ODBC escape sequence for calling stored procedures.
Cmd.CommandText = "{CALL Employees.GetEmpRecords(?, ?)}"
Is this also the case with Oracle 8.1.7? What about using using the Oracle 8.1.7 provider against the 8.1.6 engine?
cmd.CommandType = adCmdStoredProc. All this works fine. I'm wondering however, if I can increase performance by using the Oracle provider for OLE DB, BUT I don't want to change my ADO code just for that. Can I use the Oracle provider for OLE DB without having to use the ODBC call syntax? I've tried chaning my connect string to the Oracle provider but I get error messages saying that I have the wrong number of parameters for my stored procedures. I've seen this on a few Web sites as an example of ADO code with the Oracle provider:
' ODBC escape sequence for calling stored procedures.
Cmd.CommandText = "{CALL Employees.GetEmpRecords(?, ?)}"
Is this also the case with Oracle 8.1.7? What about using using the Oracle 8.1.7 provider against the 8.1.6 engine?