I just started to experiment with replication:
I made a design master, I made replicas.
Then I changed the content of fields, all propagated well through
synchronization.

I inherited a number of Access databases from previous employees. A
week or so ago I started to get the error message that the replica was
about to expire and needed to be synchronized. Not knowing if or where
the master existed and seeing no need therefore to synchronize I left

I received an urgent call from a customer. One of their replicas will
run out of the retention period in the next 24 hours. Is there any way
to increase the period for this replica?
Lothar Geyer

Need major help.
Have ~80 client replicas that sync to 4 network replicas.
All 4 network replicas display the corrupt message when manually opening
them with Access, indicating I need to synchronize with the Design Master to

An application of ours that is implemented on user PCs w/runtime uses DAO to
automatically synch BE replicas to the main server Design Master BE replica
when the notebook/tablet PCS users are connected to the office LAN. This all
works fine until design changes are required in ...