Re: Conflict resolution window no longer opens

"Anne M." <amayer@xxxxxxx> wrote in
news:1168533121.217485.197530@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:

David W. Fenton wrote:
"Anne M." <amayer@xxxxxxx> wrote in
news:1168457039.412321.50400@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:

I tried your suggestion and the "Conflict Viewer" still does
not pop up, therefore making it impossible to resolve the
conflicts. However, I noticed in my Tables, there were new
table names, such as Owner_Conflict. Is it possible to resolve
using these tables? It only shows the fields from one database
so I cannot determine which field is having the conflict.

One last thing: have you tried running the standalone conflict
resolver? This should be in your [program files]\common
files\microsoft shared\Database Replication folder (where
[program files] is usually c:\program files). The wizard can be
run directly from there, and then you point it at the replica you
want to test for conflicts and it may be able to load them and
allow you to resolve them.

THAT WORKED!!!!! I have the Replication Conflict Viewer. I
assumed it existed somewhere on my HD but had no idea where to
look. I guess from now on I will just have to use that path to
get to the conflict viewer instead of it popping up automatically
like it use to... I can live with that. Thanks a million!

Actually, once you delete your existing conflict tables, normal
functioning should return.

If you want to use the standalone conflict viewer, it can be
launched with the VBA Shell command. There was a discussion of this
very subject buried in the very huge thread on Homegrown Replication
that was some troubleshooting of the arguments you pass (turns out
they have to be passed in a particular order). If you use that you
could create a command button in your app to launch the conflict
viewer.

But I believe it's likely that once you've resolved the stubborn
conflicts, you'll have normal functionality back.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.