We have one specific requirement for an application that if there is a conflict between the publisher and subscriber, we want the users to manually resolve it themselves. I've looked into the Windows Synchronization Manager and that does not meet our
requirements. As a result, we're going to roll our own conflict resolving interface custom to our application.
The SQL Server 2005 replication meets all of our needs except for the custom conflict resolution. I'm trying to write a custom resolver (using the Microsoft.Samples.SqlServer.BusinessLogicHandler. I've overridden the UpdateConflictsHandler method,
but I don't see a way to ignore conflicts via the ActionOnUpdateConflict enumeration; all the choices are to accept either the custom, default, publisher, or subscriber data.
Is there a way to ignore conflicts via a custom resolver? If not, is there any suggestion on how to do something like this?
Thanks,
Kyle
