SosySuddefs
New Member
I'm calling a stored procedure to generate an ADO recordset and I'd like to be able to update the data before outputting it (but not write those updates back to the DB).Is this even possible and if so, how?I've tried a number of cursor and lock types but they either error out immediately or when I try to update a recordset field. \[code\]io_oRecordSet.CursorLocation = adUseClientio_oRecordSet.Open oDataCmd, , adOpenStatic, adLockOptimistic, adCmdStoredProc... iterate through RS ...io_oRecordSet("myCol").value = "http://stackoverflow.com/questions/15670498/foo"\[/code\]This one generate the following error \[quote\] Microsoft Cursor Engine error '80040e21' Multiple-step operation generated errors. Check each status value.\[/quote\]From what I've seen I suspect that ADO might not like that the data is coming from a stored procedure since it wouldn't know how to do a DB update.