Ken:

  Joining deleted with inserted worked. Thanks.

  I still don't know why joining deleted with history needs the update to be issued twice to work.

Tried both.

Using UPDATE(col1) OR UPDATE(col2)... for all columns doesn't fire the trigger, even if I really update a column.

Using exists needs the update command to be issued twice to work. Weird....

Sorry Antares, didn't see your previous question: 750.000 rows. Twelve satisfying the where clause.

Yes. Both servers autostart DTC.

Yes. Same bad performance.

Same if using a variable (datetime), storing the value and comparing the remote date against it. Only working when value is "hardcoded".

Nothing. It has 5 rows.

If running in 2k or later, you can use a Trigger instead of INSERT and store

the offending value in a table.

Regards,

Hernan