Conflict Management

Hello:
If merge replication uses anonymous pull subscriptions and
the subscribers have no sql server tools installed, how can the
subscribers resolve conflicts? (Can we provide a program interface to
help do this?)
Does replication(merge) preserve transactional integrity
while doing updates to the publisher, if there is a conflict. (That
is, if a updated table, that was updated in a transaction on a
replicated database, conflicts with another replicated database, since
this information waits in conflict tables till resolved, will the
whole transaction wait or will the remaining tables proceed to update
themselves?)
Thanks for the help,
Hananiel
The conflict viewer is one possibility. I believe this ships with Office
2003. The SQL 2000 Resource kit has a chapter devoted to the Conflict
Resolver object. You might want to build your own conflict resolver app.
"Hananiel" <hananiel@.yahoo.com> wrote in message
news:e338e321.0410110813.771d55a8@.posting.google.c om...
> Hello:
> If merge replication uses anonymous pull subscriptions and
> the subscribers have no sql server tools installed, how can the
> subscribers resolve conflicts? (Can we provide a program interface to
> help do this?)
> Does replication(merge) preserve transactional integrity
> while doing updates to the publisher, if there is a conflict. (That
> is, if a updated table, that was updated in a transaction on a
> replicated database, conflicts with another replicated database, since
> this information waits in conflict tables till resolved, will the
> whole transaction wait or will the remaining tables proceed to update
> themselves?)
> Thanks for the help,
> Hananiel