Error using ADO recordset to add a record
14170Jan 19 2004 — edited Feb 5 2004I have one deployment where our software (ASP, VB COM components, Oracle database) is failing with the following error:
error 80040e21
Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
Multiple-step OLE DB operation generated errors
I consider myself experienced in these issues and suspect this is something to do with ADO/MDAC talking to the Oracle ODBC Driver. The driver is version 8.1.5.5 (is that a correct number - could be 8.1.7.5 - still waiting for confirmation).
Basically my VB code does this:
- Calls rs.Open() on the table
- Calls AddNew()
- Loops through and sets each of the fields. We have run into issues with Oracle and setting nulls/empty strings in this way so this is carefully avoided and they are updated later.
- Closes the recordset etc...
The error happens during the loop (don't all errors!) but it's odd - after the loop has been through and set pretty much every type of column, dates, varchar2s, numbers, it suddenly falls over setting a NUMBER column to a value of "5" (no quotes!). From debug it is clear that setting NUMBER columns works earlier in the run.
This code works and has worked for a long time against SQL Server and Oracle. This server is new as the client is moving an old installation to this new server. They have another installation which works fine. We have major checked versions (MDAC, ODBC driver), ODBC driver settings and so on but no joy - nothing seems any different from their working installation.
Sorry to harp on. Either there's a really simple explanation or something a bit bizarre going on. Gut says it's the server environment as it works in so many others and that is what has changed but what could it be?
Can I use ODBC tracing or anything like that to get "real" info on the rather faceless ADO/OLEDB error?
BIG thanks for any help.