These pages refer to legacy Hydra and Lycia 1 features.
The functionality described here does not embrace all the functionality provided by Lycia 3.
If you use Lycia 3, please, turn to other sections of this online documentation.
These pages refer to legacy Hydra and Lycia 1 features. The functionality described here does not embrace all the functionality provided by Lycia 3. If you use Lycia 3, please, turn to other sections of this online documentation.
COMPRESS keyword prevents blanks produced by the editor from being included in the program variable.
COMPRESS is applied by default and can cause truncation to occur if the sum of intentional characters exceeds the field or column size. Because of editing blanks in the WORDWRAP field, the stored value might not correspond exactly to its multiple-line display, so a 4GL report generally cannot display the data in identical form.
To suppress COMPRESS, specify UNCOMPRESS after the WORDWRAP keyword. This option causes any editor blanks to be saved when the WORDWRAP string is saved in a database column, in a variable, or in a file.
Default value is COMPRESS.
In the following fragment of a form specification file, a CHAR value in the column charcolm is displayed in the multiple-segment field whose tag is mlf:
SCREEN SIZE 24 by 80
{
Enter text:
[mlf ]
[mlf ]
. . .
[mlf ]
[mlf ]
}
TABLES tablet . . .
ATTRIBUTES
mlf = tablet.charcolm, WORDWRAP COMPRESS;
If the data string is too long to fit in the first line, successive segments are displayed in successive lines, until all of the lines are filled or until the last text character is displayed (whichever happens first).
If the form is used to insert data into tablet.charcolm, the keyword COMPRESS specifies that 4GL will not store editor blanks.