I have this database that I set up using Replication Manager. It was working fine. The machine that I had the replication manager had Access 2000 re-installed on it. Now the databases won't synchronize. I even tried to synchronize manually between the design master and another replica. I get this error: "The search key was not found in any record. (Error 3709)". I even took the design master, created a replica from it. Can't synch them either? Any thoughts? This thing use to work fine. Also, every time I open a replica, it says there are conflicts. Do I say yes or no to resolving them? Thanks for any input!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Replication Problems
- Thread starter wild007
- Start date
wild007
i've got the same message in access while trying to change a date even at the Table level. All was ok but then...
Seems i had set an INDEX on the datefield. I'm not sure i need one but removing the index seems to help. I still haven't tested totally [but i can change the date so i'm going to bed now!].
Hope this has some relevance to your situation.
i've got the same message in access while trying to change a date even at the Table level. All was ok but then...
Seems i had set an INDEX on the datefield. I'm not sure i need one but removing the index seems to help. I still haven't tested totally [but i can change the date so i'm going to bed now!].
Hope this has some relevance to your situation.
- Thread starter
- #3
Thanks for the reply. It turns out that it might have been one of the machines. I talked with Microsoft and they said that one of the know problems causing this is different versions of the Jet engine and recommended getting all machines to Jet 4.0 SP5...still didn't take care of it, so they assumed bad network activity. The funny thing is that when I create a replica on this one machine from a design master, it is the only one that gets corrupt out of the four other replicas out on the network. The one odd thing that I did notice was that when I made a datatype change in one of the tables in the design master, it created the same error message in all of the remaining "good" replicas. Each is running on it's own synchronizer. I've since reverted back to the backup of the non-replicated backend and am getting away from Synchronization on that network. I have it running on three other networks, without ANY incidences. I'm going to chalk this one up to "not every network likes replication"...until I hear otherwise. Thanks again for your reply though.
- Status
Similar threads
- Locked
- Question
- Locked
- Question