Informix Error -1312: FORMS statement error number number.
Cause and resolution
FORMS statement error number number.
A problem exists with a screen form. Look up error number in this document. Consider it in relation to the current statement.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-1312 is a wrapper message: it reports a problem with a screen form and embeds a second, specific error number in its text — per the official guidance, that embedded number should be looked up separately and considered in relation to the current statement.
- A form-processing error whose specific cause is identified by the embedded error number, per the official guidance — -1312 itself is generic; the embedded number carries the actual diagnostic detail.
Solutions / Resolution
- Look up the embedded error number in the error-code reference, per the official guidance, and address it as its own specific condition.
- Consider the embedded error in relation to the current statement, per the official
guidance, since the wrapping
FORMS statement errorcontext matters for interpreting it.
Examples
Reading the embedded error number
FORMS statement error -1102.
-- -1312 wraps -1102 here: "Field name not found in form" —
-- look up and resolve -1102 specifically
Diagnostic Checks
- Extract the embedded error number from the -1312 message text, and look it up as its own specific error.
Related Errors / Related Topics
- -1313 — "SQL statement error number number." A related wrapper-error message, for a database-server-detected SQL error rather than a forms-processing one.
- -1315 — "4GL run-time error number number." A related wrapper-error message, for a general 4GL runtime error.
The specific related error beyond these wrapper messages depends entirely on the number embedded in the -1312 text itself.
A generic forms-error wrapper — look up the embedded error number for the actual diagnostic detail.