a table trigger and merge replication and nullable columns

[amar...@comporium.net]

We're using merge replication, and there are triggers on tables in
other databases that update a replicated table. There is an after
insert trigger on 1 table, which updates values of several columns in
a replicated table. It seems that when the trigger fires and updates
columns to the replicated table, the columns that are updated to NULL
do not get pushed to the subscriber. If the columns are updated to a
value that is NOT NULL, the changes DO get pushed.

Is this by design? We plan on getting rid of crappy database design
in the future, but for now I was wondering if there was something that
could be done. (I've been running a tablediff each day and updating
to the subscriber).

Thanks,

Amy