What type of replication are you setting up? Also are you sure you want to use the same publication table to do differnt things...altho i am sure that it can be done..it seems to me that it might cause confusion as you would have one publication table doing multiple things. I have never had to do what you are asking so my answer is very general and my apologies for that. I would think that IF by any chance you could set this up with less complexity you will be better off in the long run but if not that is totally understandable, replication alone is a monster depending how well its set up and to add complexity like this....careful what you wish for

The Type of replication I am doing is merge replication and I have a two hop setup where I have

Publisher->Publisher Subscriber(Republishing Server)->Subscriberand I am also using Web Synchronization from the Republishing Server to the Subscriber with a PULL setup on the Subscriber.

The subscriber is on SQL 2005 Express SP3 btw and the Publishers are all on sql 2005 SP3.

When I try and create another publication on a table with Automatic Identity Key management i get the above error.

The reasoning behind wanting to try out having multiple Publisher entries for the same table is due to the he table in question being a Global table across multiple companies and each subscriber only cares about data from their company so if i createa publication for each company then each subscriber consumes less data.

I agree that Replication is a Monster and the less you have to manage the better but as a first stepI would like to give it a test and see how it behaves.

If anyone has any personal experience with this issue and can offer some advice it would be appreciated.