Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Replication / August 2005

Tip: Looking for answers? Try searching our database.

Conflict Resolution Viewer Won't Display Conflicts

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Abster - 24 Aug 2005 03:37 GMT
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 viewer
that behaves differently on different computers. I am able to view conflicts
and resolve them just fine on my computer but on another computer, when you
hit the view conflicts button nothing happens. The other computer is running
Access 2002 but I have tried it on Access 2000 and 2002 and can view/resolve
without problem.

We are both running the same version of the msjet40.dll (4.0.8618.0) but the
other computer has a different version of the conflict resolution viewer
(different than either of the ones that come up for me using 2000 or 2002). I
tried copying my wzcnflct.exe file to their computer and launching manually
with same results. I also copied my .mdw file to their computer and used it
thinking maybe it was a permissions issue...no luck.

I thought maybe something was wrong with the conflict data so I created
another "normal" conflict to see if I could resolve it...no luck.

Interestingly enough, other computers within the same organization give the
same results, although one computer actually gave me a message at one point
in the process saying that "the database you are attempting to connect to is
not a replica". What is that all aboutf??!!

Any thoughts? TIA
Mark - 24 Aug 2005 07:44 GMT
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
David W. Fenton - 24 Aug 2005 21:36 GMT
> 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?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.