Note The information in this topic applies only to a Microsoft Access database (.mdb).
Some of the content in this topic may not be
applicable to some languages.
You can use one of the following methods for replicating (replication: The process of copying a database so that two or more copies can exchange updates of data or replicated objects. This exchange is called synchronization.) and synchronizing (synchronization: The process of updating two members of a replica set by exchanging all updated records and objects in each member. Two replica set members are synchronized when the changes in each have been applied to the other.) databases:
Briefcase replication
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 (replica: A copy of a database that is a member of a replica set and can be synchronized with other replicas in the set. Changes to the data in a replicated table in one replica are sent and applied to the other replicas.). 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 (Design Master: The only member of the replica set in which you can make changes to the database structure that can be propagated to other replicas.) 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:
Replication in a Microsoft Access project
A Microsoft Access project (Microsoft Access project: An Access file that connects to a Microsoft SQL Server database and is used to create client/server applications. A project file doesn't contain any data or data-definition-based objects such as tables and views.) file contains several wizards to help you create a publication (publication: In an Access project, a publication can contain one or more published tables or stored procedure articles from one user database. Each user database can have one or more publications. An article is a grouping of data replicated as a unit.) and subscription (subscription: The database that receives tables and data replicated from a publisher database in an Access project (.adp).). 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 (Microsoft Access database: A collection of data and objects (such as tables, queries, or forms) that is related to a particular topic or purpose. The Microsoft Jet database engine manages the data.)
replica (replica: A copy of a database that is a member of a replica set and can be synchronized with other replicas in the set. Changes to the data in a replicated table in one replica are sent and applied to the other replicas.).
Implementing replication programmatically
Use Jet and Replication Objects (JRO) (JRO: A set of automation interfaces that you can use to perform actions specific to Microsoft Jet databases. Using JRO, you can compact databases, refresh data from the cache, and create and maintain replicated databases.) if you require programmatic control over the exchange of data and design information among members of the replica set (replica set: The Design Master and all replicas that share the same database design and unique replica set identifier.) in Microsoft Access databases (Microsoft Access database: A collection of data and objects (such as tables, queries, or forms) that is related to a particular topic or purpose. The Microsoft Jet database engine manages the data.) (.mdb files only). For example, you can use JRO to write a procedure that automatically synchronizes a user's replica (replica: A copy of a database that is a member of a replica set and can be synchronized with other replicas in the set. Changes to the data in a replicated table in one replica are sent and applied to the other replicas.) 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) (Data Access Objects (DAO): A data access interface that communicates with Microsoft Jet and ODBC-compliant data sources to connect to, retrieve, manipulate, and update data and the database structure.) to programmatically replicate and synchronize it.
Web server replication
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.