The grid, tree view, Web browser, status bar, and ActiveX controls, as well as pop-up menus, are only partially imported.
For these controls, common properties and styles are imported. However, control-specific properties and styles are ignored
and must be added manually.
Only controls are imported. Screen elements described by textual fields (for example, DISPLAY "CUST NO") are not imported.
The imported screen does not retain any of the structural information in the original source's Screen section. For example,
if a Screen section item contains subsidiary group items, that information is lost. The Screen Designer cannot represent these items, so they are not imported. The resulting screen has the same look as the original, but a different
internal structure.
Importing a screen and then generating code may result in an illegal COBOL program. This can happen when the original source
code contains structures that have no representation in the Screen Designer. For example, if the original program contains two fields that have the same name, but are distinct using qualification by
intermediate group items, the resulting program may be illegal as the intermediate group items are lost. In another example,
if the USING phrase for a control names a qualified data item (for example, MY-DATA OF MY-GROUP), then the resulting program
contains an illegal data declaration (for example, 01 MY-DATA OF MY-GROUP PIC X(10)). You can adjust for these anomalies in the Screen Designer after importing the screen.
If both FROM and TO are specified, the TO item becomes the control's VALUE and the FROM item is ignored. Otherwise, any specified
FROM/TO/USING item becomes the control's VALUE. The control's actual VALUE is suppressed, but the VALUE data item name and
picture are imported.
CLINE, CCOL, CSIZE, and CLINES are not currently imported.
MULTIPLE VALUE items have the word Table in front of their data item name. However, the number of occurrences in the table is not imported.
For entry fields, list boxes, and combo boxes, if neither BOXED nor NO-BOX is specified, the import utility sets BOXED to
true (although FIELDS-UNBOXED can affect this). While this is an accurate reflection of the control's appearance under Windows,
this could change the look under character systems. You might want to leave both BOXED and UNBOXED false and have the Screen Designer assume the BOXED appearance. Also note that FIELDS-UNBOXED implies the NO-BOX style (for entry fields) at the time the control
is created. This is reflected in the imported code even though NO-BOX is not specified in the original source.
Labels always have a LABEL-OFFSET of 0. The label offset value is reflected in the coordinates for the label.
Single-line entry fields report their MAX-LINES as 0, because MAX-LINES is meaningful only for multi-line entry fields.
CURSOR and ACTION properties are not imported for entry fields. These fields are not normally used in a Screen section.
For list boxes, the following properties are not imported: MASS-UPDATE, ITEM-TO-ADD, RESET-LIST, ITEM-TO-DELETE, INSERTION-INDEX,
SEARCH-TEXT, SELECTION-INDEX, QUERY-INDEX, and ITEM-VALUE. All of these are dynamic properties that are not part of the static
appearance of the list box. You may want to reconsider ITEM-TO-ADD and possibly others.
For combo boxes, the following properties are not imported: MASS-UPDATE, ITEM-TO-ADD, RESET-LIST, ITEM-TO-DELETE, and INSERTION-INDEX.
For frames, FILL-PERCENT is not imported.
For tab controls, RESET-TABS and TAB-TO-DELETE are not imported.
For bars, one dimension has a size of zero. Use the value of the WIDTH property to determine the actual width of the line.
For bitmaps, either SIZE or LINES may be zero. In this case, the full size of the actual bitmap should be used for the corresponding
dimension.