Once a replica is created and in-place, don't move it. In
particular, don't use email, floppy disk, USB drive, etc as a
method of synchronizing. Doing so will eventually corrupt your
database.
For the gold-standard discussion of this concept, see this website:
http://trigeminal.com/usenet/usenet009.asp?1033
Each replica has a unique "serial number" or replicaID. One of the
hidden replication tables contains a list of all known replicas and
their locations.
*Every* time that the Jet database engine opens a replica, it confirms
that the place from where it opened the replica (ie, the current
computername, path, and MDB filename) matches *exactly* with its
internal record of where that replicaID is known to reside. If they
are found to be different, then the replica is considered to be a new
one, and a new replicaID is added to the list of known replicas. The
old replicaID is now useless.
Therefore after a "two-way transfer" of your database you will have
created two new replicas. The Jet database engine maintains all the
information that is required to keep these replicas up-to-date, but
since they can never be accessed again, they are "dead". Useless.
Consuming resources.
Eventually, carrying all this excess baggage will corrupt your
database. Only way to prevent it from happening is to not move
replicas. Just don't do it!
On Sun, 27 May 2007 19:04:56 +0100, "Les Girvan"
<lj_N05pam_girvan[ at ]hotmail.com> wrote:
[Quoted Text] >Hi Guys,
>
>Just trying to get up to speed on replication and just wondering if my
>thought process on this is OK?
>
>We will have a 'server' be db and each staff member will have a copy on this
>to use on their laptop. Each day they will send back their be db, each staff
>member will have a folder for each staff member.
>
>I will then set the sync to the 'server' with the a fully sync version to be
>mailed out to each staff member.
>
>We currently have 7 staff to use this database...is this viable?
>
>Regards
>Les
--
jackmacMACdonald[ at ]telusTELUS.net
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
|