Replication PK/FK conflict

We have established a Report server (subscriber) for our
OLTP production database (publisher). Transaction
replication is running between the two databases.
An UPDATE on the OLTP database is triggering a
DELETE/INSERT on the Report database. This DELETE is
causing a FK conflict and results in replication errors.
It appears that if an UPDATE is done on an index key, this
causes a DELETE/INSERT instead of an UPDATE. Is there any
way to handle this without dropping the FKs on the Report
(subscriber) database in replication?
Thanks
Jay,
this is a known issue. There is a solution though:
http://support.microsoft.com/default...NoWebContent=1
hth,
Paul

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~