VisualAge Generator to Enterprise Generation Language Migration Guide

Fields at row=0, column=0

VisualAge Generator: VisualAge Generator 4.5 tolerates fields positioned at row=0, column=0 from older releases of Cross System Product or VisualAge Generator. However, VisualAge Generator 4.5 did not provide a way to create fields at this position. You could not set attribute information for fields positioned at row=0, column=0.

EGL: EGL does not support fields positioned at row=0, column=0. Every field must include an attribute byte.

Associated part needed for migration: Not applicable.

Figure 29. Fields at row=0, column=0

Migrating with the associated part
Migrating without the associated part

When migrating a form, if a field is positioned at row=0, column=0, the migration tool does the following:

  • If the field is a constant field and the first character of the value is blank, the migration tool does the following:
    • Removes the first character from the value and reduces the field length by 1.
    • Sets the position property to (1,1).
    • Includes default presentation properties for the field.
    • Issues a warning message.
  • If the field is a constant field and the first character of the value is not blank OR if the field is a variable field, the migration tool does the following:
    • Does not change the value or the field length.
    • Sets the position property to (0,0).
    • Includes default presentation properties for the fields.
    • Issues an error message.

The migration tool does the same thing as mentioned in the Migrating with the associated part column.

Potential Problem 1: If the field cannot be changed and is at position=(0,0), there will be an error on the Tasks list.

Solution 1: Modify the form and change the position of the field. You might need to move other fields or reposition constants to make room for the attribute byte for the field. Also review the default presentation properties to ensure that the correct color, highlighting, and so on are used.

Potential Problem 2: If a constant field is changed to position=(1,1), there might be a different runtime appearance due to the default presentation properties.

Solution 2: Review the migration warning messages and be sure to test any forms where the migration tool adjusted the position of a field.

Potential Problem: The same problems listed under the Migrating with the associated part column can occur. You can use the same solutions.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]