"rkusenet" <rkusenet@sympatico.ca> wrote in message news:<bckh61$jlnp9$1@ID-75254.news.dfncis.de>...
> > Yes, I'm updating the same table, but not the same record. I need
> > recalculate the carrying operation's balance :(
>
> From what I understand, you can not do this. Plus I am bit
> baffled by the logic. On each row works row by row. And you
> are trying to do an update operation on the same table.
> I am not sure whether it can be serializable.
>
> However, you can try this.
>
> use FOR EACH ROW to store values of pre.cuentaorigen ,pre.cuentanum
> ,pre.cuentadc ,pre.idproducto ,pre.idoperacion, etc in a dynamically
> growing global string (LVARCHAR).
>
> Then use an AFTER DELETE Trigger to use the same string, de-parse
> it and then update the table. Since AFTER DELETE
> trigger do not work on a row by row basis, the end result will be
> serializable and may even avoid -747 error. I am not sure, you
> have to try this.
>
> The only problem with this approach can be, that you can not update
> too many rows, as LVARCHAR is limited to 2K in pre 9.40 release.
> In that case u can temp table instead of LVARCHAR.
Thank's for this suggestion. I'll do this. Thank's