Have you tried unregistering and re-registering the wzcnflct.exe file by
running it with the /UnRegServer and then /RegServer flags?
Cheers
>I have been dealing with replicated databases for a few years now and I am
> stumped. I have an Access 2000 application with a conflict resolution
[quoted text clipped - 32 lines]
>
> Any thoughts? TIA
> I have been dealing with replicated databases for a few years now
> and I am stumped. I have an Access 2000 application with a
[quoted text clipped - 24 lines]
>
> Any thoughts? TIA
Have you tried repairing the Office XP installation on the
problematic machine?
Have you also checked the permissions of the user you're running it
under? Perhaps the user logon doesn't have permission to run the
conflict viewer.
Or maybe it's incompletely installed and for some reason, the
installer is not fixing it (that's why I suggested the repair).

Signature
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Abster - 25 Aug 2005 17:45 GMT
Thanks to you both for the prompt responses. Long story short, it appears
that there was some corruption in the replica set somewhere. I tried the
stuff you guys suggested and nothing seemed to work so I created a test
database and replicated it, created a conflict with a replica and was able to
view/resolve without problem.
Since we were early in the implementation, I just created a new database and
imported everything into it and re-replicated. Purposely created a conflict
and viewed/resolved without a problem.
I guess the problem is "fixed" for the time being but it is aggravating that
I couldn't identify the actual issue. And the fact that I could view/resolve
using my computer when they couldn't bugs me, too. I would welcome any
theories!
Thanks again.
>> I have been dealing with replicated databases for a few years now
>> and I am stumped. I have an Access 2000 application with a
[quoted text clipped - 11 lines]
>Or maybe it's incompletely installed and for some reason, the
>installer is not fixing it (that's why I suggested the repair).
David W. Fenton - 25 Aug 2005 20:14 GMT
> Thanks to you both for the prompt responses. Long story short, it
> appears that there was some corruption in the replica set
> somewhere.
I assume that it was a type of corruption that was not resolved by
compacting the database?

Signature
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Abster - 25 Aug 2005 22:37 GMT
Correct...tried that.
>> Thanks to you both for the prompt responses. Long story short, it
>> appears that there was some corruption in the replica set
>> somewhere.
>
>I assume that it was a type of corruption that was not resolved by
>compacting the database?