7.4

l Parse normally: Select to interpret any backslashes included in the database connection string as back-
slashes. If this option is not selected, any backslash that is not doubled will be disregarded.
l Expect record set:Check if you are expecting a result from the database after executing the SQLquery. If
the query is expecting a record set in return and does not return one, the task will trigger an error.
l Database connection string: Enter a variable connection string in this box. To do this you may begin by
clicking to create an ODBC connection string to the data source and paste the string automatically to this box.
Note that if a login name and password are required to connect to the database, a dialog box is displayed and
the information you enter is saved in the configuration of the PlanetPress Database action task. Another option,
if a database connection string (not a database path and name) was already entered in the Database Connection
tab, is ti simply copy and paste it to this box. Bear in mind that if the Parse normally option is not selected, any
backslashes included in the connection string that is not doubled will be disregarded. Once your connection
string is displayed in this box, you can edit it by adding variables or data selections.
l SQL statement: Enter your SQL statement. Remember that you may use variables and data selections in
your statement.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on Task Properties Dialog.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are
being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window
will be available for the rest of your process, or whenever they are overwritten.
Common Errors
Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are
related more to the system than to PlanetPress itself. Some examples would be W3813, W3830, W3991, W4005. These cor-
respond to issues such as not having any space to write files, permission errors on folders or files, etc.
Rename
Rename action tasks are used to rename the job files they receive. Note that you can see how each file is renamed via the
Object Inspector when stepping through a process in Debug mode.
Input
Any job file, in any format.
Processing
The task renames the job file to the desired name, and changes the value of %f and %Fto reflect the new name.
Output
The input data file is output, with the new name.
Rename action task property is as follows:
General tab
l New file name: Enter the job file’s new name. In this variable property box, you may enter static characters, var-
iables, job information elements, data selections, or any combination of these.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on Task Properties Dialog.