Home > Archive > Visual Basic > April 2005 > Updating a hierarchical recordset
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Updating a hierarchical recordset
|
|
|
| I have a hierarchical, static, disconnected ADO recordset.
I attempt to update one of the fields in it:
--------------------------------------------------------------
with oRS
Set oUniqueRow = .Fields
end with
.......
' I attempt to update the field:
oUniqueRow .Item("crossRefCatID").Value = 20
--------------------------------------------------------------
I get the error:
Run-time error '-2147217887 (80040e21)
Multiple-step operation generated errors. Check each status value
Any ideas?
Thanks
Griff
| |
|
| INFO: Using Disconnected Hierarchical Recordsets:
http://support.microsoft.com/kb/q213856/
Read Part 1 and Part 2:
http://www.4guysfromrolla.com/webtech/060301-1.shtml
--
Chris Hanscom - Microsoft MVP (VB)
Veign's Resource Center
http://www.veign.com/vrc_main.asp
--
Read. Decide. Sign the petition to Microsoft.
http://classicvb.org/petition/
"Griff" <Howling@The.Moon> wrote in message
news:%236KzitNTFHA.612@TK2MSFTNGP12.phx.gbl...
> I have a hierarchical, static, disconnected ADO recordset.
>
> I attempt to update one of the fields in it:
> --------------------------------------------------------------
> with oRS
> Set oUniqueRow = .Fields
> end with
> ......
> ' I attempt to update the field:
> oUniqueRow .Item("crossRefCatID").Value = 20
>
> --------------------------------------------------------------
> I get the error:
> Run-time error '-2147217887 (80040e21)
> Multiple-step operation generated errors. Check each status value
>
>
> Any ideas?
>
> Thanks
>
> Griff
>
>
>
>
>
| |
|
| Okay - I think the problem is slightly different.
I know how to create a SHAPE command and retrieve data back from the
database. I'm returning this to a DLL and processing the recordset entirely
within the DLL, not passing it to another process.
The problem is that when I attempt to CHANGE a field value within the
recordset (not UPDATE the underlying database) I get the error mentioned in
the original post.
A bit more info...
The field value that I'm attempting to alter exists in the TOP recordset
(presumably this shouldn't make a difference).
The field in question was originally created as a "place holder", i.e. by
saying "SELECT NULL AS PlaceHolder" and I'm now saying
..item("PlaceHolder").Value = ABC, causing the error.
Wits end on this one!
Thanks
Griff
|
|
|
|
|