Translating or converting field values using a table

For mark, character, object, and selection fields, you can use a table to change one field value to another.

Instructions – part 1: Creating the table

Using Manager, select File ð New.
In the New object dialog, select Table and click New.
Type a name for the new table. Note that table names are case sensitive.
Click OK. The Table dialog is displayed.
In the first box of the Update line, type values that can occur in the field. Type one key value on each line. The Key field can contain up to 63 characters.
Type the value to which you want to change each key value on the same line under Translation. The Translation field can contain up to 99 characters.

If you want the value to be replaced by spaces, type one space as the translation value. (If the field on the form definition is numeric, you must also change the transaction field type from numeric (N) to alphanumeric (X) to accommodate the space. Also, you may want to change the pad character, as the default pad character for alphanumeric fields is a space. Do all of this in the Transaction description dialog.)

There is no need to fill in the Connection 1 and Connection 2 columns, though you can fill these in if you intend to use the table for validation via a connection table, as well.
Click Close. This saves the table.

Create or edit the field definition in your form definition.
On the Advanced tab of the Field dialog, type the name of the table in the Translation table box.
Optional: Select Translate when transferred to translate the value after validation and verification (that is, just before transfer) rather than before.

Important: If you select Translate when transferred, the transferred field must be included in the transaction description associated with the form definition. If it is not included, it will not be translated. This is true even if the actual transfer is handled by a FORMS customization.

If you do not select Translate when transferred, translation occurs in Interpret. To avoid validation errors in this case, make sure the format specification of the field being translated matches both the field values and the translation values. FORMS does not support direct translation of different field formats via table translation. In other words, you can not translate a field with a numeric format specification to an alphabetic value. This can be accomplished, however, using a connection table connected to an empty field.

Note: By default, the original field value (not the translated value) is saved to the form if you select Translate when transferred. If you want the translated value to be saved to the form, set SaveTranslatedValues in the [Transfer] section of Ehlocal.ini to 1.