Karl Hennermann <karl.hennermann@manchester.ac.uk> wrote in
news:ebkt12$14uo$1@godfrey.mcc.ac.uk:
The method you are using is *not* an option that you should be using
at all -- it's producing 2 dead replicas for every synchronization
cycle (once on the project manager end, and once on the field staff
end, and that's for each field staff member). Dead replicas will
eventually lead to synchronization problems and eventually to an
inability to even synch at all.
You need to switch to one of the other methods for synchronizating
data, either indirect/Internet replication over the Internet, or by
having them synch directly when they are in the main office.
There is no other way to do this that is safe and reliable.
As soon as they were opened in the field, they became plain old
replicas.
They aren't both masters -- only the design master is the master.
The copies of the DM are simple replicas as soon as they are opened
in a different location.
The error message is just telling you that Jet thinks another user
is editing the data. This is a common error message indicating some
form of corruption or a corrupted locking file (LDB). Try deleting
the LDB file (for both partners in the synch). If that doesn't work,
try compacting both partner replicas.
Last of all, your project manager shouldn't be using the DM for
anything at all. He should be using a plain old replica to synch
with all the other replicas, and keep the DM somewhere else safe and
synch with it only about once a month to make sure it doesn't
expire.
In short, you're doing a whole host of things that are bad practices
for replication. I'd suggest you read the archives of this newsgroup
and the articles on replication at trigeminal.com and clean up your
procedures. Failure to change your ways will eventually lead to far,
far worse problems than the error you're getting right now.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
|