what the hell...

Results 1 to 3 of 3

Thread: what the hell...

  1. #1
    Join Date
    Dec 1969

    Default what the hell...

    ...does this error mean?<BR><BR>Microsoft OLE DB Provider for ODBC Drivers error &#039;80020009&#039; <BR><BR>Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. <BR><BR>/index.asp, line 0<BR>

  2. #2
    Join Date
    Dec 1969

    Default Line zer? Cool.

    Haven&#039;t a clue why you get "line 0".<BR><BR>Normally this error is associated with:<BR>1) A transaction, where one step in the transaction failed, or<BR>2) Using the ADODB.RecordSet to update a field, but one of the values provided is the wrong datatype (or too long, etc).<BR><BR>Craig.

  3. #3
    Join Date
    Dec 1969

    Default *SOMETIMES*...

    ...you can find the cause of this.<BR><BR>First, you have to figure out what line *really* caused the error.<BR><BR>Then do this:<BR><BR>&#060;%<BR>...<BR>conn.Errors.Clear<B R>On Error Resume Next<BR>[[[ the line that causes the error goes here ]]]<BR>On Error GoTo 0<BR>For Each oops In conn.Errors<BR> Response.Write "DB Error #" & oops.Number & ": " & oops.Description & "&#060;br/&#062;"<BR>Next<BR>Response.End &#039; optional, but might as well<BR>..<BR>%&#062;<BR><BR>"conn" is of course the name of your connection variable, change as needed. No guarantees. Worth a trial.<BR><BR><BR>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts