Oninit
Talk to an expert →

Informix Error -1109

-1109 List and record field counts differ.

The number of program variables does not agree with the number of screen fields in a CONSTRUCT, INPUT, INPUT ARRAY, DISPLAY, or DISPLAY ARRAY statement. Review the statement in conjunction with the form specification to see where the error lies. Common problems include a change in the definition of a screen record that is not reflected in every statement that uses the record, and a change in a program record that is not reflected in the form design.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-1109 fires when the number of program variables in a CONSTRUCT, INPUT, INPUT ARRAY, DISPLAY, or DISPLAY ARRAY statement doesn't match the number of screen fields in the associated screen record — per the official guidance, this requires reviewing the statement alongside the form specification to locate.

  1. A screen record's field count changed in the form specification without updating the matching program statement, per the official guidance's named common cause.
  2. A program record's field count changed without updating every statement that references the corresponding screen record, the mirror-image version of the same underlying inconsistency.
Solutions / Resolution
  1. Review the statement alongside the form specification, per the official guidance, to count fields on both sides and find the mismatch.
  2. Update whichever side is out of date — the screen record in the form, or the program record/variable list in the statement — so the counts match.
  3. Check every statement using the affected screen record, per the official guidance, since a record change can leave more than one statement out of sync.
Examples
A mismatched field count
-- form specification's screen record "s_order" has 4 fields
-- program code:
INPUT BY NAME order_id, status, total FROM s_order.*
-- -1109: 3 program fields vs. 4 screen fields in s_order
Diagnostic Checks
  1. Count the fields on both sides — the screen record in the form specification, and the variable list in the program statement — and reconcile the difference.
  2. Check every other statement referencing the same screen record, in case more than one is affected.
Related Errors / Related Topics
  • -1102 — "Field name not found in form." A related form-processing error, about a single field name not resolving rather than a count mismatch.
  • -1108 — "Record not in form." A related form-processing error, about the screen record itself not existing rather than its field count disagreeing.

The program and screen record field counts disagree — review the statement against the form specification and reconcile whichever side is out of date.