Merge Replication issue (dupe key)

My invoice header table has a primary key of Location# and Invoice#. If a
subscriber does the following…
Creates invoice with the primary key of Location 4, Invoice 100.
Replicates the data.
Deletes the record and recreates it.
Replicates.
I will get an duplicate primary key entry in the conflict table.
Is this because the replication ROWGUID is NOT the primary key?
Thanks,
Steve
Steve,
the ROWGUID doesn't need to be the PK and almost always shouldn't be the PK.
When you delete the record on the subscriber are you adding the record back
on the publisher before synchronizing, or are you adding the record back on
the publisher? I'll try to duplicate this behaviour once you post back.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
Everything is happening on the subscriber. Is created there, replicates,
deleted and recreated on the subscriber, then replicates again.
Thanks,
Steve
"Paul Ibison" wrote:

> Steve,
> the ROWGUID doesn't need to be the PK and almost always shouldn't be the PK.
> When you delete the record on the subscriber are you adding the record back
> on the publisher before synchronizing, or are you adding the record back on
> the publisher? I'll try to duplicate this behaviour once you post back.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Steve,
sorry but I still can't replicate this. Perhaps there is something else
happening? Is the record changed on the publisher at any time? Also, can you
post up the exact error message.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
Thanks for trying to replicate this and help us out. We are fairly
inexperienced in this area.
The merge agent history is showing conflicts on the last replication, but
the conflict resolver doesn't show any. Not sure how to find them. It says
28 resolved conflicts, how can I see what they were?
After looking into the situation more, there may be some other (user)
things going on which we will need to investigate further. The may be
updating and replicating from multiple P.C.'s in a manner we did not
anticipate.
After talking with them, if we can not determine what is going on, we may
have to ask again with more details.
Thanks again,
Steve
"Paul Ibison" wrote:

> Steve,
> sorry but I still can't replicate this. Perhaps there is something else
> happening? Is the record changed on the publisher at any time? Also, can you
> post up the exact error message.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>