Re: Unmanaged replica is being synchronized violently

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Cheval (NoSpam.Ask_at_ForEmail.com)
Date: 01/18/05 

Date: Tue, 18 Jan 2005 21:52:31 GMT

No. Rule that suspicion out. Access treats replication like another user.
eg, The replication manager can add, edit and delete data in a replica. The
only difference is that instead of its data source being the keyboard (text
file, ODBC, etc), it's another replica. That also means that if a record is
in use or locked, the replication cannot work with that record. I have
multiple replica databases open to up to 50+ people while I run
synchronizations and the only issues I ever have are locking ones. So as I
said below this will not cause a corruption...itself! I have see replication
corrupt a database when the network is of poor quality though. To read about
that, see my postings from October/November last year, when I was pulling my
hair out over that.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>
"Ingo Hueser via AccessMonster.com" <forum@AccessMonster.com> wrote in
message news:9fdec584bdc741f181cb4ea279864a7d@AccessMonster.com...
Hi Cheval,

Thanks for your prompt reaction.

>Is the direct replication done totally through the replication manager >or
done via requests in DAO, JRO or ADO code ?
Totally through replication mgr. ? schedule is set to synchronize every 15
min. among the replica farm members, and once/24 with the unmanaged
user-replica.

>There is also a difference in error messages between a corrupt replica >to
an expired replica. What does the error message exactly say?
I know, those expired replicas did not seem to be corrupt at all, they were
just excluded from the set somehow. Upon trying to synchronize the replica
directly in Access, an error message popped up that was like ?This replica
is not part of the replica set anymore and is removed form the list of
replicas.? When opening the replication mgr. That manages this replica, a
similar message popped up and the whole replication set was gone.

>What version of Access?
Access 2000, the American version.

>Are all the replicas giving you this exact message when you perform a
>manual replication from the Access Tools->Replication->Synchronize >Now?
For some reason the last replication date isn't being updated. >Unless
someone else knows how to update the last replication date, you >will need
to re-create the expired replicas from the most current non->expired one.
I have replaced all the expired ones with new ones, not always from the most
current non-expired though. Now everything seems to work fine again, apart
from this replica that is not intended to synchronize every 15 min.

>BTW, it doesn't matter if a replica replicates every 15 minutes, >Access is
fine with that.
I?d agree if all replicas were closed, but this one unmanaged user-replica
is open all the time since this is the replica where internal users are
supposed to work with. I suspect this regular synchronization with the open
replica to be the reason for the initial incidence of db corruption and want
to avoid this in the future. 

-- 
Message posted via http://www.accessmonster.com
Quantcast