"Tigermikefl" <Tigermikefl@discussions.microsoft.com> wrote in message
news:0AEA83CE-9A6A-4A81-A503-D840A9A3CD15@microsoft.com...
>I have a merge replicated table with a composite pk. One field unique id,
> the other a float. SQL2Ksp4 and msde subs, anon.
>
> I get conflicts 'The row was inserted at SERVER but could not be inserted
> at SUBSCRIBER....Violation of PRIMARY KEY ...Cannot insert duplicate key
> in
> object 'XXX'.'
>
> This doesn't bother me if the subscriber re-insert fails, they already
> have
> the data. However, it seems to do a double-delete to resolve the problem
> and
> deletes the good row from the live Publisher. After reinserting again on
> the
> Publisher, it eventually disappears again and repeats.
>
> I switched to the 'later date wins' conflict resolver hoping for relief
> but
> it didn't help. I could care less which guid wins, as long as one does.
>
> How do I stop this cycle ?
>
> --
> Mike
>
> If data falls in the woods and nobody is there to see it ....... ?