Oninit
Talk to an expert →

Informix Error -1371

-1371 The field fieldname does not exist in the current form.

The indicated field name has been given to the NEXT FIELD statement or to the pf_nxfield() function, but it is not defined in the current form. A common error is to confuse the tag name, which is used in the screen layout and to the left of the equal sign in the ATTRIBUTES section, with the field name, which is the column name used to the right of the equal sign in the ATTRIBUTES section. Use the latter when you refer to fields.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-1371 is the 4GL-program equivalent of -1119: it fires when a field name referenced in a NEXT FIELD statement or the pf_nxfield() function isn't actually defined in the current form — per the official guidance, a frequent cause is confusing the screen tag (left side of ATTRIBUTES) with the actual field/column name (right side).

  1. A field tag used where a field name is required, per the official guidance's specifically named common mistake — the same confusion as -1102's tag-vs-name mistake.
  2. The form changed without updating the referencing NEXT FIELD/pf_nxfield() call, per the same general cause as -1119.
Solutions / Resolution
  1. Use the correct field name (not the tag) when referencing fields, per the official guidance — check the ATTRIBUTES section's right side for the actual field name.
Examples
N/A

This is the 4GL-program wording of -1119's condition — see -1119's examples for the underlying tag-vs-field-name mechanism.

Diagnostic Checks
  1. Check the form's ATTRIBUTES section to confirm which side is the tag and which is the actual field name, per -1119's diagnostic approach.
Related Errors / Related Topics
  • -1119 — "NEXT FIELD name not found in form." The non-4GL wording of this same field-name resolution mistake.

The 4GL-program wording of -1119's field tag-vs-name confusion — see -1119 for the full detail.