Records Deleted after merge

PKs and FKs are all uniquidentifiers.
(the db will eventually have 100's of subscribers)
The FK validation errors only occur sometimes - this the odd thing.
And when it does happen it is on new records added by one subscriber, so
there shouldn't be any conflicts.
Thx
You may get the behavior you describe if your foriegn keys are missing the
"NOT FOR REPLICATION" option.
|||Thanks Jim.
Any idea where can I get more details on this behaviour?
Darren
|||I haven't seen any documentation on this yet but basically you cannot
guarantee that replication will apply your changes in the order that they
originally occured.
"Darren Wallace" wrote:

> Thanks Jim.
> Any idea where can I get more details on this behaviour?
> Darren
>
>
|||Thanks Jim.
Pity about that.
So it sounds like all foreign keys should have the Not For Replication
option.
Cheers
Darren