Replication - Conflicts

Hello,
I read in articles that there can occur two kinds of conflicts during
replication and that the SQL Server Reconciler solve such conflicts:
1) If more subscriber try to modify a row on the publisher database at the
same time.
2) If a certain row is modified at the subsriber database as well as the
coresponding row at the publisher database. So any one of those two have to
win and the other win will accept the changes of the other side.
So how does it look like when the Reconciler solve these two conflicts. How
does it work?
thx
rob
Hello,
Sorry that I posted the same question twice but it was accidentally. But
unfortunately this information is very important for me. Does no one knows
how the SQL Server Reconciler solves these conflicts (propagated by Hilary
Cotter)?
1) primary key collisions, where the publisher and subscriber enter a row
with the same value for the primary key between merge agent runs
2) a row is updated on the publisher or subscriber and deleted on the
subscriber or publisher. When the merge agent runs it attempts to update a
row which no longer exists.
3) you update the same row on both sides of a replication solution and do
not have column level tracking enabled for your publication.
Thank you very much in advance.
Regards
mat