You should NOT replicate the IDENTITY property. Try using the ROWGUIDCOL instead and set the Default property to NEWID().
This should take care of your problem.
Rick Sawtell MCP, MCT, MCSD
10 Million Lemmings Can't Be Wrong
We are merge replicating two tables who have identity fields.
The publication table has an identity seed of 1 and an increment of 10.
The subscribing table has an identity seed of 2 and an increment of 10.
After the first replication everything works as planned, but after the second replication, SQL server changes the identity seed of the subscribing table to 1.
In the snapshot properties of the publication, we indicate that if a table with the same name exists at the subscriber SQL should delete all records (using truncate)
We do not replicate indexes or keys.
In the subscription we indicate that sql should not initialise the shema and data, in order to preserve the difference in identity seeds.
I think we filled in all the options correctly ?!