Violation of constraints

If you say that there IS NOT a duplicate key then you dont have a problem :o)
Or maybe there is!

How to I do check for this without running through all the data from replicator?

Well to be honest I dont use replication so I wouldnt know the easiest method. This is taken from Books Online, which I suggest you read.

Conflicts Occur When Merging Newly Inserted Rows That Contain Identity Columns
If conflicts occur when merging newly inserted rows that contain identity columns, use the Replication Conflict Viewer to determine the cause of the conflict. An insert conflict is usually caused by inconsistent enforcement of constraints between Publishers and Subscribers. Also, identity columns must be used with caution. You must assign each Subscriber that will insert new rows containing an identity a unique range of identity values.

I am not using ms sql inherited replicator technique but are using osql - well maybee there is somewhere a check for constraints perhaps on the recieving table......

no idea waht osql is :o(

Tag og benyt UIID som Nøgle istedet for! De er garanteret til at være Unique på denne jord!

Jeg mener selvfølgelig GUID!