Oninit
Talk to an expert →

Informix Error -1102

-1102 Field name not found in form.

A field name listed in an INPUT, INPUT ARRAY, CONSTRUCT, SCROLL or DISPLAY statement does not appear in the form specification of the screen form that is currently displayed. Review the program logic to ensure that the intended window is current, the intended form is displayed in it, and all the field names in the statement are spelled correctly.

A common problem is the attempted use of field tags instead of field names. The field tag is the name that is written in the screen picture and that appears at the left side of the ATTRIBUTES statement for that field. It is not the name of the field for input or display purposes. The field name is the column name with which it is associated. This name appears to the right of the equal sign in the ATTRIBUTES section.

ATTRIBUTES

f000 = customer.customer_num,color=red;

The name of the field in the preceding example is customer_num. Use of the tag f000 in an INPUT statement will produce an error.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-1102 fires when an INPUT, INPUT ARRAY, CONSTRUCT, SCROLL, or DISPLAY statement references a field name that doesn't exist in the currently displayed form specification — per the official guidance, the most common mistake is using a field's screen tag instead of its actual field name.

  1. A field tag used where a field name is required, per the official guidance's specifically named common mistake — for example, using f000 (the tag shown in the screen picture and on the left of the ATTRIBUTES section) instead of customer_num (the actual field/column name, shown to the right of the equals sign in ATTRIBUTES).
  2. A genuine typo or outdated field name, referencing a field that was renamed or removed from the form specification since the statement was written.
Solutions / Resolution
  1. Check the form specification's ATTRIBUTES section, per the official guidance, and use the actual field name (right of the =), not the screen tag (left of the =).
  2. Confirm the field still exists in the current form specification, if it was recently modified.
Examples
Using a tag instead of the field name
-- ATTRIBUTES section of the .per file:
-- f000 = customer_num;

INPUT BY NAME f000  -- -1102: f000 is the tag, not the field name
Corrected
INPUT BY NAME customer_num
Diagnostic Checks
  1. Check the form's ATTRIBUTES section to confirm which side is the tag and which is the actual field name, and correct the statement to use the field name.
Related Errors / Related Topics
  • -1103 — "This value is not among the valid possibilities." A related form-processing error, about a value failing an INCLUDE list rather than a field name not resolving.
  • -1104 — "The two entries were not the same. Try again." A related form-processing error, about a VERIFY field's mismatched double-entry rather than a field name issue.

A field tag was used where the actual field name was required — check the form's ATTRIBUTES section for the correct name.