The business application shouldn't encounter many conflicts of data caused by replicas simultaneously updating the same data. Resolving conflicts isn't agreeable to users and will be time-consuming.
Focus on applications where data is more often inserted, rather than where existing data is updated. The only exception is where you can guarantee that all updates will occur at a single site, and therefore conflicts between replicas will never occur.
Replication provides data on a “real-time-enough” basis to remote sites. If your business application requires up-to-the-second synchronizations, consider a two-phase commit solution, not Access replication.
Although conflicts should be rare, you can reduce ...