7.2

Table Of Contents
Microsof Word® needs to be installed for this task to be functional and to test the connection.
General tab
l Microsoft Word Document: Enter a Microsoft® Word® document or template, or click the browse button to navi-
gate to the location of the document. The supported extensions are: *.doc, *.docx, *.dot and *.dotx.
l Perform Mail Merge: Check when providing a Microsoft® Word® document or template configured for mail merge.
l Use settings specified in document: Selected to instruct the task to use the connection string and SQL
statements stored in the DOC file. There is no guarantee that the database, connection string or statement are
still valid, especially if the DOC file was moved or sent to someone else.
l Use custom settings: Override the mail merge settings in the Microsoft® Word® document and lets you
specify your own.
l Connection String: The connection string to any ODBCdatabase supported by PlanetPress Suite. You can
use the Browse button to open an existing File DSN, or use the Database Button to open the ODBCconnection
interface.
l SQL Statement:An SQLstatement that is understood by the database you are using and that will return a
series of records that the Microsoft® Word® template is expecting. Note that no validation is made on
SQLstatements except if they are for Microsoft Access and Excel data files. You can use the Test Connection but-
ton to test the SQLand connection string.
l Test connection: Checks if the Connection String and SQLStatement are valid, and if the resulting recordset
is understood by the Microsof Word® document. This is optional, though highly recommended.
l Output Type:
l .PDFFile (with metadata):The result will be a PDFfile with the number of pages generated by the com-
bination of the template and recordset. Metadata is also included that complement the PDF.
l .DOCfile:The result is a Microsoft® Word® document in .doc format. Note that this format is not supported
by PlanetPress Suite as a data file or job file, so this option is only useful if you are simply planning to save the
Word document in a specific location.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on "Task Properties Dialog" (page 53).
Notes
l Microsoft Word must be installed on the PlanetPress Suite Workflow Tool system.
l Microsoft Word must not be currently opened when the automation task runs.
l Microsoft Word 2003 and up are supported.
l The task uses a printer queue set with the “PlanetPress Word to PDF Printer” driver, which is created and set by default
on-the-fly the first time a Microsof Word® Document to PDFAction Task is run. This printer cannot be shared on the
network in order to avoid confusion from network users, however it is shared between all Microsoft® Wor Doc-
ument to PDFaction tasks on the same system.
l While debugging this task, the printer shows the message that the document can not be printed. This message is nor-
mal and will not appear when running a live configuration.
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 Microsof Word® document, the mail merge has to be performed with the set-
tings specified in the document, otherwise the database path provided in the task is ignored and can cause different con-
flicts. To use custom settings, the Microsoft® Word® document should contain only mail merge fields with no database
path entered. The Microsof 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.
©2010 Objectif Lune Inc - 130 -