The system in question is a ASP/SQL Server web application. It has been in production for about a month now and most of the time, there are no problems at all. I know because I've set up the system to send e-mails on all errors generated from the DB communication and they don't come often. However, sporadically (5-6 times now), I've recieved an e-mail that states: -2147467259: Microsoft Cursor Engine Data provider or other service returned an E_FAIL status. Because of some other debugging information in the e-mail, I know where this is coming from. Keep in mind the functions shown simply error trap the actual commands, which will be explained in italics: Note: The actual code will be in bold, while comments in italics. 'Step 1: Init the Recordset call InitRS(pConn, tmpRS, "FormsArchive", 3) 'InitRS executes tmpRS.Open(sSQL, pConn) after setting parameters 'FormsArchive is sSQL, the 3 simply specifies the following parameters 'tmpRS.CursorType = 1 'adOpenKeyset 'tmpRS.LockType = 2 'adLockPessimistic 'tmpRS.CursorLocation = 3 'adUseClient 'Step 2: Get the recordset ready for the Add if not RSAction(tmpRS, "Add") then DeliverErrorMessage(pConn) '"Add" specifies to do an tmpRS.AddNew tmpRS.Fields("FA_FDFFile") = pFileName tmpRS.Fields("FA_PDFID") = pFileID tmpRS.Fields("FA_Description") = pFileDesc tmpRS.Fields("FA_Timestamp") = Now() tmpRS.Fields("FA_Userstamp") = Session("User") 'Step 3: Complete the Add and update the DB if not RSAction(tmpRS, "UpdateBatch") then DeliverErrorMessage(pConn) '"UpdateBatch" specifies to do an tmpRS.UpdateBatch I don't know exactly where the error is coming from (Step 1, 2, or 3), but my guess is that is comes from Step 3. Any ideas?