2018.1

avoid confusion from network users, however it is shared between all Microsoft® Word®
Document to PDF action tasks on the same system.
l If using a Microsoft® database such as Access® or Excel®, each software must be
installed in the same version. For example, using Microsoft® Word® 2007 with a
Microsoft® Access® 2003 database will cause the task to fail.
l If the database path is specified in the Microsoft® Word® document, the mail merge has
to be performed with the settings specified in the document, otherwise the database path
provided in the task is ignored and can cause different conflicts. To use custom settings,
the Microsoft® Word® document should contain only mail merge fields with no database
path entered. The Microsoft® Word® to PDF action task allows specifying the path of the
database and the query to use. The Use custom settings option is very usefully for using
different databases and queries in a single process.
l If the database is the same for 2 processes, one of two processes aborts. Each process
has to use different databases, or no more than one process with a Microsoft® Word® to
PDF task.
Input
A compatible Microsoft Word Document.
Processing
The Word document is converted into a PDF file. If a Mail Merge is made, the mail merge is
done in the document before the document is converted into a PDF file. The conversion is done
through the use of a printer queue - the document is printed to this queue and the print job is
converted to PDF. This is the same technique as used in the "WinQueue Input" on page248
when generating PDF files.
Output
The output is either:
l A PDF file accompanied with basic PDF metadata. This is the default output. The
Metadata contains one Document level, and one Data page (and Page) level for each
PDF page generated by the document. When Mail Merge is not selected, this is the only
available choice.
Page 371