ADO 2.7: Multiple-step operation generated errors
- From: "Mike Jansen" <mjansen_nntp@xxxxxxxx>
- Date: Mon, 22 Aug 2005 14:21:52 -0400
I'm receiving "Run-time error '-2147217887 (80040e21)': Multiple-step
operation generated errors. Check each status value." when attempting to set
a value in a field:
rs.Fields("MyField").Value = 0
I'm fairly certain I know what's causing this error. The column that this
field comes from is a constant value in the query, e.g. SELECT 0 As
MyField, ..., ..., ... FROM MyTable, so the dynamic properties
BASETABLENAME, et. al. are all blank.
The scenario in our application is this: The data is loaded into a
RecordSet and then disconnected. The app never intends to update the
database from this particular recordset but does want to change values in
the recordset just in-memory.
So my question is this: Is there any way to alter the record set schema to
allow me to change the value in a field that has no back-end reality? When
I open the recordset is there a way to say "don't bring any of the back-end
schema along because I don't want any smart validation"?
Thanks,
Mike
.
- Follow-Ups:
- Re: ADO 2.7: Multiple-step operation generated errors
- From: Matt Neerincx [MSFT]
- Re: ADO 2.7: Multiple-step operation generated errors
- Prev by Date: Re: Excel Euro Symbol Issue
- Next by Date: Re: Trapping CommitTrans - returns success even when failed!
- Previous by thread: Excel Euro Symbol Issue
- Next by thread: Re: ADO 2.7: Multiple-step operation generated errors
- Index(es):
Relevant Pages
|
|