Hello Reg,
it's not really an update conflict.As I said it seems that the consolidated checks the verify clause and sends back column updates.
It looks from the logs that the consolidated is getting the messages out of sequence. It sends the 'correction' and then applies the update correctly. The consolidated ends up with the correct data and 'inadvertantly' makes the remote incorrect.
The trouble is that the data that got corrupted at the remote this last time could cause, shall we say, a nasty medical problem. We need a way to say 'stop trying to correct things'.
Paul