7.1

Table Of Contents
Database Splitter action task properties are as follows:
General tab
l Split group: Use this group to indicate how you want the file to be split.
l Field value change: Select if you want the file to be split based on changes in the values of a selected database field
(the value in the ClientID field changes, for example).
l Field value condition: Select if you want the file to be split based on a condition set for the values of a selected data-
base field (the value in the Order field equals 1, for example).
l Field count: Select if you want the file to be split whenever a given number of pages or data pages has been reached.
The following options are only displayed when the Field value change or the Field value condition option has been
selected at the top of the dialog box.
l Field: Enter the name of the field upon which to base the splitter condition. Note that you can use the popup menu's
Get Data command to select the field and populate this box automatically.
l The following options are only displayed when the Field value condition option has been selected at the top of the dialog
box.
l Operator: Select the condition to fulfill for the condition to be true and thus for the splitting process to take place.
l Value: Enter the condition value. Note that you can use the popup menu's Get Data command to select the value and
populate this box automatically
l Match case: Select to force the splitter to match the character casing when resolving the Field value change or Field
value condition. If this option is selected, a change from “DAY” to “Day” will be considered as a valid field value change,
and “DAY” and “Day” will not be considered as equal values.
l Where to split group: Options from this group are used to define a number of pages or records before or after
which the file is to be split.
l Pages or records: Enter the number of pages or records before or after which the file is to be split. Enter 0 if you
want the file to be split right before or after the page or record that matches the set condition.
l Before or after: Options from this list box are used to define exactly how the file is to be split. Select Records before
if you want the file to be split a given number of records before the field that matches the set condition. Select Records
after if you want the file to be split a given number of records after the field that matches the set condition. Select Pages
before if you want the file to be split a given number of pages before the field that matches the set condition. Select
Pages after if you want the file to be split a given number of pages after the field that matches the set condition.
l Split when condition is found group: Use this group if you want the condition to be met a multiple number of
times before splitting the file. Leave the default value of 1 in the Times box if you want to split the file every time the
condition is met, but enter a value of 2, for example, if you want to split the file every second time the condition is met.
l Time(s): Enter the number of times the condition must be met before the file is to be split.
The following options are only displayed when the Field count option has been selected at the top of the dialog box.
l Maximum records per file: Enter the maximum number of records to include in each file. Enter 0 for no limit.
l Maximum pages per file: Enter the maximum number of pages to include in each file. Enter 0 for no limit.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on "Task Properties Dialog" (page 51).
Emulated Data Splitter Action Task Properties
Emulated Data Splitter action tasks are used to split emulated data files (with the exception of XML and database data files -
refer to "XML Splitter Action Task Properties" (page 138) or "Database Splitter Action Task Properties" (page 133)) into mul-
tiple data files that are passed to subsequent tasks in the process.
The data received by the process is typically prepared for a given output device using a pre-set emulation. In some cases, the
data’s original emulation may also have been changed by a Change emulation action task (see "Change Emulation Action Task
Properties" (page 112)).
©2010 Objectif Lune Inc - 134 -