7.6

Channel skip emulation options
l Skip page: Enter the code used within the data to mark the beginning of each page (the number 1 in standard channel
skip emulation). Note that if the standard code is used within the data as the skip page code, it is likely that the other
codes are also standard, and that you only need to make minor changes to the other codes, if any.
l No line feed: Enter the code used within the data to indicate that the next line feed character should be ignored. This
causes the next line to print over the current line, and is a technique impact printers use to print a line, or elements of a
line, in bold or with underlining.
l Skip [x] lines: Enter the code used within the data to indicate that the corresponding number of lines must be
skipped.
l Char and Skip to line: Enter the code used within the data to mark a jump to a different line in the Char box, and
enter the corresponding line number in the Skip to line box.
l Char and Go to column: Enter the code used within the data to mark a jump to a different column in the Char box,
and enter the corresponding column number in the Go to column box.
Database Emulation
This emulation differs from other emulations in regards to PlanetPress Suite applications. With other emulations, data is
pushed either to PlanetPress Design documents residing on printers or to PlanetPress Suite Workflow Tool processes running
on servers. But in the case of the database emulation, data must be pulled from the data source.
Like with every other emulation, it is possible to send a PlanetPress Design document set up to use the database emulation to
a printer. But contrary to documents that use the other emulations, you cannot send a raw data file to the document and
expect the document and data to merge and print automatically. In this case someone or something must query the database
and extract the data that will populate the PlanetPress Design document.
We can imagine two basic scenarios. In the first one, we can imagine someone in a print shop who needs to use data from a
database to print a bunch of personalized letters using PlanetPress Design. That person opens a PlanetPress Design document
and uses the Data Selector to select a database. By making a connection to the database, its structure can be accessed and it
becomes possible to determine how data is to be pulled into PlanetPress Design. The process actually pulls data into Plan-
etPress Design and lets the print shop employee visualize and print the data on the personalized letters.
The second scenario involves PlanetPress Suite Workflow Tool. In this case, PlanetPress Database action task takes the place
of the print shop employee and performs the database query automatically. The task generates a PlanetPress Design com-
patible data file that it passes to the following task, be it another action task, or any output task.
Bear the following in mind:
l The person or plugin performing the query must have full access to the database.
l The data is extracted at the time of the query. A new query must be performed whenever the data needs to be
updated.
l Any changes to the structure of the database may have an impact on automated data querying tasks.
l You must have the proper ODBC driver installed to use this emulation.
Database emulation supports SQL ANSI 92 or higher, and supports the following data types: string, integer, floating point, all
date formats, and text-only MEMO. It does not support any binary data types such as Binary Large Object (BLOB), images,
sound files, and MEMO data that includes binary data.
Database emulation requires version 2.5 or higher of Microsoft Data Access Components (MDAC), including JET 4.0, and you
can save database emulation configurations to a file.
To set up a database emulation:
©2010 Objectif Lune Inc - 93 -