Error reading recordset from DB2/AS400

I am trying to use ADODB to return a recordset from a DB2 stored
procedure on AS400. All the procedure does is return a cursor for
SELECT * FROM. I have tried both the "IBMDA400" and "Client Access
ODBC" drivers. The first returns an empty recordset (incorrect), while
the second returns the expected number of records. Unfortunately,
attempting to read the field values produces the error "multiple-step
operation generated errors" at the first adDBDate field. The contents
of the remaining fields after this point are garbled. However, I am
still able to read the other information for all fields (name, size
etc).

Note that if I use the ADODB.Command to do the SELECT * FROM directly
(adCmdText), the resulting recordset works perfectly under both
drivers!

Is there any problem with interpreting recordsets obtained directly
from AS400/DB2 stored procedures, or specifically the adDBDate data
type? Thanks.

.

Relevant Pages

  • Re: Combine Recordsets
    ... >> can access the same database with a number of different drivers of your ...
    (microsoft.public.vb.general.discussion)
  • Re: Paradox 5.x table access
    ... Have you tried to make a link from MS Access to that table using ODBC? ... > I've been attempting to use a ADO recordset. ... > ODBC DSN ... > that uses my ODBC DSN (Microsoft Paradox Driver) to access successfully ...
    (microsoft.public.data.ado)
  • Re: Paradox 5.x table access
    ... Have you tried to make a link from MS Access to that table using ODBC? ... > I've been attempting to use a ADO recordset. ... > ODBC DSN ... > that uses my ODBC DSN (Microsoft Paradox Driver) to access successfully ...
    (microsoft.public.data.oledb)
  • Re: Paradox 5.x table access
    ... Have you tried to make a link from MS Access to that table using ODBC? ... > I've been attempting to use a ADO recordset. ... > ODBC DSN ... > that uses my ODBC DSN (Microsoft Paradox Driver) to access successfully ...
    (microsoft.public.vb.database.ado)
  • Re: MDAC 2.8 vs MDAC 2.7
    ... Actually RecordCount has to do with the provider, ... If just changing of the connection string to use OLEDB provider solves this ... then it looks like a bug in OLEDB for ODBC provider or in ODBC ... But do you get an actual recordset opened in your case? ...
    (microsoft.public.data.ado)