"Michael Hotek" <mhotek@nomail.com> wrote in message
news:uyVuwOeIEHA.828@TK2MSFTNGP12.phx.gbl...
> The tables requiring two-way data movement need to be in a different
> publication than the ones requiring one way data movement. (There is no
> bi-directional replication when using merge as it simply does not exist.)
> This is because the ExchangeType option is set at a publication level.
>
> [Completely unsupported and not really recommended option]
> Now....... If you really don't want two publications, you can accomplish
the
> same thing by making some system modifications. First recognizing that
> merge works through triggers. If those triggers do not fire, nothing is
> logged into MSmerge_contents which means that change will NOT propagate.
> There are three ways you can accomplish this.
> 1. Drop the merge triggers for the tables on the side that you don't want
to
> send changes back
> 2. Disable the same triggers as 1
> 3. Edit the same triggers as 1 and add a simple return command to the
first
> line.
>
> My choice would be #3 as it leaves all of teh code intact, but essentially
> renders it useless. However, it you reinitialize or apply service packs,
> you may have to reapply any of these changes.
>
> I don't recommend using this option since Microsoft and no one else will
> support you. They may try to help, but you would be entirely on your own.
>
> --
>
> Mike
> Principal Mentor
> Solid Quality Learning
> "More than just Training"
> SQL Server MVP
> http://www.solidqualitylearning.com
> http://www.mssqlserver.com
>
>