As you may have noticed with accessmailmergedemo.mdb the distributing the combination of your Access database with Access Mail Merge involves nothing more than zipping the folder and unzipping it at the destination. This works without problems under condition that
Note that if you have a developer or OEM license in the
[yourdb]_processes.xml file you will have to change the license part to
<License ProductName="Mail Merge for Microsoft Access" LicensedTo="your company" LicenseCode="YOUR-LICENSE-RUNTF-ZOXUU-AMMST" MaxUsers="999" Type="Runtime" />
Generally is considered good practice to split an Access database. For one reason, it reduces the chance of the database getting corrupt. The backend contains the data, The front-end the application (forms, queries,...).
If your network is not slow then this is an option which makes taking in production of a new version of the front-end easy. In this scenario you can work as described under Single User, the only difference being the database is split.
In this scenario you should make sure the processes definition file is put next to the backend database (is shared). You will use the file [yourdatabase]_processes_redirect.txt to tell the Mail Merge library where processes definition file [yourdatabase]_processes.xml is located. You can choose either to simply keep the Tools folder with the front-end or put it in a shared folder. You will probably want to specify a shared folder where you keep the templates.
This works the same way as above, the difference however is that you additionally will have to change the reference of the Front-end to the Libraries new location: