Can you modify your publication to set compensate_for_errors to be false?
This will prevent the errors from being wiped out.
It is troubling that they are not being retained? Conflict tables are purged
after the retention period has past. I take it that this is not the case.

Signature
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
>I have a few subscribers that are complaining of dropped data in one of the
> main tables that users update on the subscriber machines. When they
[quoted text clipped - 13 lines]
> Jeff Jones
> Atlanta, GA
J Jones - 30 May 2006 12:28 GMT
Hilary,
Thanks for your help - I will see about setting the compensate_for_errors to
false. And, yes, the conflicts are dropped from one merge to the next, but
the subscription is active for 14 days. Very strange behavior that I've not
been able to track down the cause of...
Jeff
> Can you modify your publication to set compensate_for_errors to be false?
> This will prevent the errors from being wiped out.
[quoted text clipped - 18 lines]
> > Jeff Jones
> > Atlanta, GA