Briefcase replication is perhaps the easiest way to implement replication and is a convenient tool for keeping a database file up-to-date. You can replicate the database on your laptop by using Briefcase replication, disconnect the laptop from the network, and then make changes to the data in the replica. When you are finished working on the files on the laptop computer, you can then reconnect to the network, and automatically synchronize any changes between the database on your laptop and the Design Master on the network.
Replication commands on the Microsoft Access Tools menu
Microsoft Access provides replication menu commands that you can use while working in your databases. By using the Replication command on the Tools menu, you can:
- Create a replica.
- Synchronize your replica with another member of the replica set.
- Resolve synchronization conflicts by using the Conflict Resolver.
- Recover the replica set’s Design Master, if necessary.
Replication in a Microsoft Access project
A Microsoft Access project file contains several wizards to help you create a publication and subscription. Access projects support push, pull, and bi-directional synchronization.
In an Access project, you replicate the data, not the forms, reports, and other objects that are contained in the project. And an Access project cannot contain a Microsoft Access database replica.
Implementing replication programmatically
Use Jet and Replication Objects (JRO) if you require programmatic control over the exchange of data and design information among members of the replica set in Microsoft Access databases (.mdb files only). For example, you can use JRO to write a procedure that automatically synchronizes a user's replica with the rest of the set when the user opens the database. To replicate a database programmatically, the database must be closed.
If your database was created with Microsoft Access 97 or earlier, you must use Data Access Objects (DAO) to programmatically replicate and synchronize it.
Web server replication is a tool you can use to work on files even when you are no longer connected to a Web server.
Microsoft Office 2003 users can continue to work on shared documents even when they log off the network. When the Web Publishing feature is installed, a replication mechanism automatically maintains a list of recently opened Web server documents and stores copies of them in a cache on the local hard disk. To add files to the cache, users select a file in Microsoft Windows Explorer, and then use menu options to make the files available offline.
A user can open and edit replicated files while offline. Then, the next time the user logs on to the network, all changes the user has made are automatically replicated to the server. Also any changes that have occurred on the server while the user has been offline are replicated locally.
Note Only Microsoft Internet Explorer 5.01 or later supports offline caching and replication.