Understanding When Replication Isn't Appropriate

Despite the many positive aspects of replication, it is not appropriate in a few situations, such as when data consistency is critical. If an application requires that data be current at every given moment, it isn't a good candidate for replication. Replication is also not effective when many different users modify a large volume of existing records throughout the day. In a situation such as this, resolving conflicts that happen when multiple users update the same record isn't practical. Furthermore, you cannot utilize replication if you are using Visual SourceSafe to manage the development process. Finally, you cannot rename or move design masters, and a design master that becomes corrupted can ...

Get Alison Balter's Mastering Access 2002 Enterprise Development now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.