Merge Published Date Column wont replicate/accept NULL.

[Kevin J]

I have a table published using merge replication. There are a number of
subscribers.

One of the subscribers has a problem with a date column. When I try and set
the value to a NULL (NULL's allowed in DB) at the subscriber, the value is
accepted. But aftet the agent runs, the value is back to the value from the
publisher. If I try and NULL the value at the publisher, the value is never
accepted and returns back to the previous value.

The above is only true with NULL's. If I set the value to another datetime,
it works just fine in both directions.

SQL Server 2005 SP3 on all servers. Windows 2003 R2.
--
Kevin J

[Paul Ibison]

Are nulls allowed at the subscriber? Perhaps this is a compensating cvhanges
issue if they aren't....
HTH,
Paul Ibison

[Kevin J]

NULLS are allowed at the publisher.
--
Kevin J

[Paul Ibison]

Any check constraints or triggers involved?
HTH,
Paul Ibison

[Kevin J]

No constraints or triggers.

When I attempt to NULL the value in a SQL statement, it returns '1 row
affected', but when I check the table the value is still not null.

--
Kevin J

[Paul Ibison]

I'm stuck! Can you run a trace on the publisher and do the insert - see if
this gives more info. We need to see if we can find what's doing the change.
Also do the insert in a transaction and select the row immediately
afterwards - just to check it goes in.
Thanks,
Paul