this seems to be a bug in replication snapshot creation. we ended up changing the table to

CREATE TABLE [TimeSlices].[BaseDate](

[PK_Integer] [int] IDENTITY(1,1) NOT NULL,

[TargetDate] [date] NOT NULL,

CONSTRAINT [PK_BaseDate] PRIMARY KEY...

yes, i am replicating between sql2008 and sql2008.

regards,

for development and unit testing we are replicating on the same server.

for QA and production we are replicating between 2 or more servers then.

regards,

Chris

thank you very much, thats the solution

thanks a lot for your help, we will go with XML then

one of the scenarios we are dealing with is updating or inserting rates for flights for the next year. this has multiple different rates for business, economy, loyalty programs,... so...

we wanted to avoid the additional coding for the XML and also the overhead of the XML.

therefore we chose this solution. but obviously this doesnt work with MS SQL 2005.