Access 2002 conflict resolution not working.

> The windows 10 machine notices the replication conflict and asks if I want to resolve it

where is the location of the DBF files? already copied to the local drive of Windows 10 or still staying on where it was and accessing the files over a shared folder?

The files are local to the windows 10 machine.

if so, how do you open the files using Access 2002? the details about how you open the files using command or GUI?

BTW, why Access 2002 aka Access of Office XP?

I use the access GUI. It worked fine on my windows 7 machine. An application was developed in Access 2002 and it also provided for replication since I have and outside user doing entry and integrating with my  system. I also like the 2002 interface much better than the later interface. I've had to move it to a windows 10 machine since the Windows 7 machine is going to be used for another purpose.

>  it also provided for replication since I have and outside user doing entry

when you saw that message, was there a user doing data entry at that moment?

no

I would check the directory security on the directory where the DB's are and as a test, make sure it's set for "everyone" with full rights.

 Only thing that comes to mind at the moment.

Jim.

I have 2 mdbs. One doesn't get an error and the other one gets errors even though it requires the same components as the one without the error. I have attached 4 images. 1 - the good references of the good mdb. 2 - the error reported in the other mds 3 - the erroneous references 4 - the corrected references. I compile the corrected references and don't get an error. When I exit the bad mdb and come back, the error reappears. I believe that if I can get it to stick, the resolve conflicts error may also disappear. How can this be corrected?
good-references.png
rep-master-reference-error.png
bad-references.png

corrected-and-compiled-references.png

If you can compile cleanly without the reference, then remove the reference on the master, compile and save.   Then sync everything up.

Make sure you have a backup of everything before you start playing with it.

Jim.

I can't compile cleanly without replacing the reference. How do I get it to save the reference?

<<I can't compile cleanly without replacing the reference. How do I get it to save the reference?>>

 I must be missing something here because if you set the reference, then it should stick.  There's nothing extra you need to do.

 You are working on the master DB yes?   Do you know if your replication was for everything or data only?

Jim.

Every time I exit the mdb, the reference changes that I made are lost when I come back in.

I assume that the replication was for data only. How can I tell if it was for both?

I think you have hit on the problem. I no longer have the machine with the design master. I copied this mdb which was the design master but is now called a replica but I need to synch it with an external mdb. Can I either set it as the design master or still synch with it as a replica?

<< I no longer have the machine with the design master. I copied this mdb which was the design master but is now called a replica but I need to synch it with an external mdb. >>

  It still should be the design master.   The flag for that is internal to the DB file and it shouldn't matter if it's moved.

<<Can I either set it as the design master or still synch with it as a replica?>>

  If you don't have the design master, you can make any replica the design master.   Tools>Replication>Recover Design Master or with Replication Manager

  Again, can't stress enough that you have current backups of everything before doing this.

Jim.

I changed it to the design master and was able to save the corrected invalid references.

The conflicts dialog comes up and asks if I want to resolve and when I say yes it does nothing. This is not really crucial but it would be better if I could find out what the problem was with the conflict resolution code.

Sorry for the delay...

First, using replication manger, look at the Synch history and see if anything stand out.  If your getting a sync failure, it should be noted.

Then, I would look for conflicts using tools, replication, resolve conflicts.

 Beyond that, I'd need to pull out old stuff as I don't remember much past this.  I do remember that the replication process could be complex (one way, two way, direct, indirect, scheduled or not, a priority algorithm, existed, etc) and all the reasons why it might fail I don't remember.

 JET Replication was not widely used.  I have encountered it only a handful of times and that was long ago.   I haven't seen a replication question like this in at least ten years.

Jim.

I don't have replication manager. I've been using replication to have someone doing entry and printing receipts offline and periodically sending me their version of the database to integrate with mine. This has worked for years.

At this point, the other person is the only one doing any work on the system right now. I probably will have this other person's database become the main one and just get a copy from her from time to time to run off of. Alternatively, I will continue doing the replication and look into dealing with the conflicts somewhat manually.

did some digging yesterday and you should be able to look at MSysExchangeLog directly in each replica for any problems without Replication Manager.    You'll need to make sure your showing hidden objects, but you should be able to view the table contents after that.

 Conflicts are stored in MSysConflicts, but that you can get at through the menus.

 You also may see <table name>_Conflict for each table where conflicts reside.  This table stores the loosing row in a conflict.  

Looking at this may point out what the problem is.

Jim.

Thanks Jim for all the insightful commentary and all others that contributed.