Replication Option

What you are referring to is a 'conflict'. Have a look in
the latest BOL for "conflict resolution, queued updating".
There are 3 types:
(1) Publisher wins and the subscription is reinitialized
(2) Publisher wins and overwrites subscriber value
(3) Subscriber wins and overwrites publisher value
In merge replication there are more, but this is because
transactional consistency is not maintained - it works at
the row level only.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Thanks Paul~

Replication issues with failed logins

I just applied instcat.sql to my SQL Srvr 2k sp4. At first it broke my replication with some cursor errors. Applying the latest instcat.sql fixed the problem, however one of the distribution agents would not start (i'm not sure if instcat had anything to do with it) giving me a "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. The process could not connect to distributor 'DistributorName'. The step failed." error.

Any suggestions would be greatly appreciated!

Thanks!

For those who experience similar problems: I simply ran distribution agent at Distributor. That fixed the issue.