> "DREAMER" <LG[ at ]ARGENTINA.COM> wrote in
> news:e0tgEFupGHA.2292[ at ]TK2MSFTNGP05.phx.gbl:=20
>=20
>> I have created only one REPLICA of one MDB (that has only tables)
>> with Access XP and have distributed 10 COPIES of same (Copy and
>> paste) to the different ones PCs in differents cities .....=20
>>=20
>> QUESTIONS:
>>=20
>> 1 - When it synchronizes the 10 copies (that in fact are the same
>> one, but copied) with the main design, I can experience some
>> problem?=20
>=20
> No, they are not the same. They have the same data and the same
> design, but as soon as they are opened, they are no longer
> identical, because each will get a new, unique ReplicaID.=20
>=20
>> 2 - When each one of those REPLICAS generate his ID, it can happen
>> that different registries are superposed, erasing data of another
>> synchronization?=20
>=20
> Eh?
>=20
> A ReplicaID is a GUID, which, as the name implies, is globally
> unique. It is calculated from machine-specific data and from the
> time it is created and cannot collide with another GUID generated
> elsewhere.=20
>=20
> The assignment of ReplicaIDs is not something you can control, and
> it's not something you should worry about.=20
>=20
> What you've done so far is just fine. Now you have to figure out how
> to synch between the replicas, in-place. That means indirect
> replication, as only a LAN is sufficiently fast and reliable to
> support direct replication (i.e., the kind of replication you get
> from the Access user interface).=20
>=20
> --=20
> David W. Fenton
http://www.dfenton.com/=20> usenet at dfenton dot com
http://www.dfenton.com/DFA/