Synchronization Failed

G

Guest

It happened again; it’s been about 3 months since I rebuilt my database and
replicated it and I go to synchronize it and it failed. Once this happens
there is no fixing it I just start over with a blank Database and import the
data from my shared DB and then replicate again. My master is on a laptop
and the replica is on a network-shared server. Does anyone have any idea how
to avoid this?
 
G

Guest

Are you getting any error messages when this happens? If so, please post the
error. This information can be very useful in searching the Microsoft
Knowledge Base (KB).

I recommend visiting Michael Kaplan's web site (www.trigeminal.com) and
reading everything that he has posted on replication.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

It happened again; it’s been about 3 months since I rebuilt my database and
replicated it and I go to synchronize it and it failed. Once this happens
there is no fixing it I just start over with a blank Database and import the
data from my shared DB and then replicate again. My master is on a laptop
and the replica is on a network-shared server. Does anyone have any idea how
to avoid this?
 
G

George Nicholson

Are you saying it's been 3 months since the last syncronization? If so, I
suspect that may be the problem. I believe that replicas have an expiration
date (2 months?) assigned to them at each sync and after that point they
will no longer be recognized as replicas.

This is not my area of expertise, so don't take it as gospel, just something
worth possible consideration.

HTH,
 
G

Guest

Hi MAT4Ron,

Here are a couple of possibilities, which have nothing to do with replication:

"Run-Time Error '3709'" error message when you enter a large amount of text
in a Memo field that contains an index
http://support.microsoft.com/?id=302525

BUG: You receive a "The search key was not found in any record" error
message when you compact a database or save design changes in Access 2000
http://support.microsoft.com/?id=301474

While the second article shown above includes Access 2000 in it's title,
often times KB articles will apply equally well for multiple versions. This
article indicates that the error can result from using a PC that has not been
updated properly with the service packs for the JET database engine. My
advice is to make sure that all PC's that are running your replicated
database have the latest service packs installed for the operating system,
Office, and the JET database engine. Here is an article that includes
information on each of these points:

How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?id=303528


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

I goes something like this; "No Search key can be found in any record"
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top