Hi Michael,

Yes! They are running both sides.
We have discovered that this happens when triggers are fired also at the other table, otherwise it would work OK.
Microsoft said it's a SQL Server 7.0 bug (see hot fix Q256649), but we are working on SQL Server 2000. We are making some tests, i will check it up.

Thanks,

Ricardo