80040e21 Multiple-step OLE DB operation generated errors. Check each
OLE DB status value, if available. No work was done.

I done extensive searching of newsgroups, the msdn site and the rest
of the web trying to find a solution to this problem. I have found
many sites offering help for this particular error message but none of
them are helpful for my particular problem. I am guessing that this
error is caused because Microsoft didn't cater for dates this low.
What I am asking is, Is there a work around for this problem? eg. can
I tell ado to treat all dates as Chars or something similar.

Can you open recordset or you even cannot do that? Could
you please post your code which reads value from that
field?

Thanks,

Val

Here is an extract of the code. I am trying to copy the recordset to a
temporary recordset. I have checked and it is not a problem with
adoTempRec because I still get the error when I do a "debug.print
adoRec(i)"

Here is the connection string:
Public Const adoConnStr As String = "Provider=MSDASQL.1;Extended
Properties=""DRIVER=Teradata;DBCNAME=pcop1;UID=;PWD=;DATABASE="""

And the part of the code that has the error:
            Set adoRec = New ADODB.Recordset
            blnExecuteComplete = False
            adoRec.Open sqlExec, adoConn, , , adAsyncExecute

            While Not blnExecuteComplete
                DoEvents
            Wend

            If blnSQLError Then
                Exit For
            End If

            Set adoTempRec = CopyRecordSet(adoRec)

            While Not adoRec.EOF And Not frmStatus.blnCancel
                adoTempRec.AddNew
                For i = 0 To adoRec.Fields.Count - 1
                    adoTempRec(i) = adoRec(i)
                Next i
                adoTempRec.Update
                adoRec.MoveNext
                DoEvents
            Wend
            adoRec.Close
            Set adoRec = Nothing
            Set adoRec = adoTempRec

Thanks to anyone who can help

Jason

January 1st of the year 100 is the earliest "date" in most of the
COM/Automation world of Windows, in which ADO is included.  This explains
the reason for the error messages.

If it's not possible to convert the source data -- assuming the 1/1/1 value
means "no date value entered", one meaningless date ought to be as good as
another -- then your only alternative seems to be checking for the invalid
value and converting it in your SQL SELECT statement itself, before ADO
attempts to fill the recordset.  A CASE clause would be used for this
purpose with SQL Server; you would need to check whether your database
supports this syntax.

This posting is provided AS IS with no warranties, and confers no rights.