question

From reading [MSDN/BOL][1], it would suggest that merge replication cannot use manual >Replication offers three identity range management options: > - Automatic. Used for **merge replication** and transactional replication with updates at the Subscriber. Specify size ranges for the Publisher and Subscribers, and replication automatically manages the assignment of new ranges. Replication sets the NOT FOR REPLICATION option on the identity column at the Subscriber, so that only user inserts cause the value to be incremented at the Subscriber. For more information, see Controlling Constraints, Identities, and Triggers with NOT FOR REPLICATION. > - Manual. Used for snapshot and transactional replication without updates at the Subscriber, peer-to-peer transactional replication, or if your application must control identity ranges programmatically. If you specify manual management, you must ensure that ranges are assigned to the Publisher and each Subscriber and that new ranges are assigned if the initial ranges are used. Replication sets the NOT FOR REPLICATION option on the identity column at the Subscriber. > - None. This option is recommended only for backwards compatibility with earlier versions of SQL Server and is available only from the stored procedure interface for transactional publications. So the answer may be to change to another replication type....... [1]: http://msdn.microsoft.com/en-us/library/ms152543.aspx