Transaction description file format

• The text file consists of three parts: a list of the transaction fields, a specification of the options, and the version number. They are described in detail below.

• Transaction description files normally have the extension .trs rather than .txt, but this is not a requirement.

• Blank lines are permitted in the file.

• Comments can be inserted on their own lines that begin with "#". FORMS ignores the content of such lines.

• All of the transaction fields must be listed first before Options and Version.

• Options and Version can be switched around, and they are not case-sensitive.

• Each line containing a transaction field must have a semicolon between each part of the transaction field. If you leave out the form name, do not leave out the semicolon that would have followed the form name. Do not put a semicolon after the expression. There are always 8 semicolons on each transaction field line.
   

At the beginning of the file, all the transaction fields must be listed. Each transaction field consists of the parts listed below, separated by a semicolon, in a specific order. This is roughly the same information you would specify in the Properties dialog. All are required except the expression, the "pad always" specification, and (in certain cases) the form definition name.

1. Form definition name. Can be left empty if the transaction description is for only one form definition. Must be included for set transaction descriptions.

2. Occurrence. When a form can occur more than once within the same set, specify which occurrence of the form (within the set) the transaction field relates to. If the transaction description is not for a set definition, use zero (0).

3. Field number in the form definition (not necessarily the same as verification order). If the field does not exist on the form (for instance, if it is a system variables), use zero (0).

4. Field name. This is a label that ties the transaction field to a real field on a form definition, to a system variable or to a value that you specify. In the former two cases, the label must be identical to the actual field name or system variable. Keep in mind that field names are case-sensitive.

5. Field index. Use zero (0) for unindexed fields and system variables.

6. Field format. Specify the justification, pad character and format you require, in that order. Example: -"*"N(2) for a numeric field with 2 digits, left-justified and padded with asterisks.

7. "Pad always" specification. If you write Compact=Y under Options (see below), you can use a one (1) here to override that setting for individual transaction fields. Use 1 if the field to always be padded, regardless of any Compact setting, and 0 if it is not. If you leave it out, the default is 0.

8. Length. Specify the maximum length that the field can have in the transaction (usually the same as the length specified in the format).

9. Expression. An expression has several uses— click for more information:

   • For specific text that you want FORMS to include in the output

   • For a default value for a field

   • For a constant or for an expression to be calculated and assigned to a numerical transaction field you create yourself

   • To express a condition for a conditional transaction field

   Expressions are not required for other fields. Do not put a semicolon after an expression.
    

After all the transaction fields are specified in the file, specify options that apply to the entire transaction description. This is the same information that you specify in the Transaction description options dialog. If you want the default options, you can leave out the Options section entirely.

1. Before the options, type [Options] on its own line in the file.

2. Type Separation= and one of these:

   • None

   • Comma

   • Tab

   • A single pad character of your choice, for example a dollar sign or asterisk.

   If the Separation line is missing, FORMS sets it automatically to None.

3. Type Compact= and Y if the transaction is to be compacted or N if it is not. If the Compact line is missing, FORMS sets it automatically to N.

4. Type QuotationMark= and Y if each alphanumeric field is to be enclosed by quotation marks or N if it is not. (Purely numeric fields will not have quotation marks.)

Example:

[Options]

Separation=/

Compact=Y

QuotationMark=Y
 

In the third part of the text file, specify the version number of the transaction format exactly like this:

[Version]

TrsFileVersion=50