Upgrading from ADO 2.7 to ADO 2.81



Recently I upgraded from ADO 2.7 to the latest (2.81).

My application was VBA based, so I had to use ADO with VB 6.0 style calling
etc. rather than using .Net (which as better support for Oracle).

My application is calling packages (stored procedures) that return the data
via refcursors in an Oracle database, and was retrieving the information
without any problems when using the 2.7 version of the MSDORA provider.

Since installing MDAC 2.81, the recordset is not populated, and an error
event is raised. The connection still opens OK, but when I call the Oracle
package via the command.execute call, no records are returned.

The oracle package returns a refcursor data type, and I know the package is
being executed, as the error code indicating "No records returned" is a
user-defined error code being raised explicitly by the Oracle package code.

Even if I change my project references to select the old ADO version (2.7)
it still doesn't work.

As there is no way to uninstall MDAC 2.8, I am contemplating re-imaging the
PC so that I can get it back to the pre-MDAC 2.8 state.

Has anyone else seen this phenomena? Are there any workarounds? Any help
would be appreciated.

Here are some further details of what I am doing:

Connection Object:
connection.connectionstring = "Provider=MSDAORA;Data Source=CRFMDEV;User
ID=xxxxxx;Password=xxxxxx;PLSQLRSet=1;"
connection.CursorLocation = adUseClient
connection.Mode = adModeRead

Recordset Object:
recordset.CursorLocation = adUseClient
recordset.CursorType = adOpenStatic

Command Object:
Set Command.ActiveConnection = connection
Command.CommandText = "package_name"
Command.CommandType = adCmdStoredProc
Command.Parameters.Append .CreateParameter("parm_name", adBSTR,
adParamInput, , modMain.strLocation)

Then I make the following call to retrieve the recordset:

set Recordset = Command.Execute

.



Relevant Pages

  • Re: Upgrading from ADO 2.7 to ADO 2.81
    ... > etc. rather than using .Net (which as better support for Oracle). ... > Since installing MDAC 2.81, the recordset is not populated, and an error ... > package via the command.execute call, ... > user-defined error code being raised explicitly by the Oracle package ...
    (microsoft.public.data.ado)
  • Re: strange behavior with copyFromRecordset/ADO
    ... >> oracle db using ADO. ... > copyfromrecordset call being at fault though since I haven't tested it ... I typically run XP, using ADO 2.8. ... I tried fetching a one million row table into recordset (using ...
    (microsoft.public.excel.programming)
  • Re: Is ADO Dead (3)?
    ... The Design of ADO ... ADO uses a single object, the Recordset, as a common representation for ... a forward-only stream of results from a database, ... where data is updated at the data source or cached locally as with the ...
    (comp.databases.ms-access)
  • Re: Is ADO Dead (3)?
    ... The Design of ADO ... ADO uses a single object, the Recordset, as a common representation for ... a forward-only stream of results from a database, ... where data is updated at the data source or cached locally as with the ...
    (comp.databases.ms-access)
  • Re: Is ADO Dead (3)?
    ... The Design of ADO ... ADO uses a single object, the Recordset, as a common representation for ... a forward-only stream of results from a database, ... where data is updated at the data source or cached locally as with the ...
    (comp.databases.ms-access)