>>>For readonly there was no problem here either - it's when they're all updatable and have sent some updates to the server.
>>>The scenario I have is that one CA creates the record, the next bizobject adds a few records into a child table and then writes the FK to it into the 2nd CA on the same table as the first one. Then a third CA on the same table is fired and just retrieves the same record. At that point, it misbehaves. Mostly (depending on what I do) it thinks that it got a record inserted into the cursor (even though that record is retrieved from the server) and does an automatic tableupdate() which generates an insert statement being sent to the SQL right away.
>>>
>>>I got it to work correctly by using .cursorFill() with a new statement. Will need some time to try Fabio's trick with .cursorRefresh(lcModifiedSelectCommand).
>>
>>Backend you were working against? .WhereType you are using ? Which PK-Type and (depending on previous answers) how created ?
>
>SQL /(20005 and 2014, possibly 2008r2 as well), pk only, int, created manually (i.e. calling a server-side function independently, before tableupdate).

Conflict strategy / .WhereType you are using ?

As this is some kind of tree/recursive table, 1st CA probably needs to tableupdate() for an error to manifest at all, but nothing written above or necessary about 2nd CA. "Same record" of 3rd CA refers to newly created record from 1st CA, last from 2nd (implying tableupdate() there, all "new" records or some greater set?

We have sometimes summary CA working on R/W tables, we have recursive tables for instance for rights, often used in security joins/filters, but probably not your scenario.