Discussion Locked

Problem syncing a replicated database

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have 8 remote sites that each input into a replica of an access 2000 database. The replica is posted to an email account we can all access and each office downloads the latest version, makes their updates and, once a week reposts it so I can syncthem all and post up the latest version, etc etc.

Works well in 7 of the sites but for some reason the eighth site version always ends up being a stand-alone version when they post it up for syncing.

I've checked that it's still in replica format when they download it but I'm baffled as to why or how it converts to stand-alone.

They are definitely using the downloaded version and not importing into a new database to make it stand-alone.

Any hints would be very much appreciated!!!

Thanx in advance
Disey

2 replies

by disey

Update:

The replicas are corrupting at several sites on an intermittent basis when more than one user is entering data. (Not all the time though which leads me to think it may be a record locking problem).

The replica becomes stand-alone when the user runs a repair however they don't lose any data.

If they send the corrupt database back me to it remains a replica on repair but loses data.

We have a workaround now where we get them to copy the replica, run a repair on one and sendme both versions so I can import the lost data into my repaired replica however this is a tedious process and we really need to determine why the problem is occurring in the first place.

Thanks again
Disey

This discussion is closed to new replies.