Informix Error -1315: 4GL run-time error number number.
Cause and resolution
4GL run-time error number number.
The program stopped because an error was detected. Look up error code number in this document. Also look for other error messages for more details.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-1315 is a wrapper message: the program stopped because an error was detected, and the specific error code is embedded in this message's text — per the official guidance, that embedded number should be looked up separately, alongside any other accompanying error messages.
- A 4GL runtime error whose specific cause is identified by the embedded error number, per the official guidance — -1315 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.
- Also look for other error messages, per the official guidance, for more detail.
Examples
Reading the embedded error number
4GL run-time error -1211.
-- -1315 wraps -1211 here: "Out of memory" —
-- look up and resolve -1211 specifically
Diagnostic Checks
- Extract the embedded error number from the -1315 message text, and look it up as its own specific error.
Related Errors / Related Topics
- -1312 — "FORMS statement error number number." A related wrapper-error message, for a forms-processing error specifically.
- -1313 — "SQL statement error number number." A related wrapper-error message, for a database-server-detected error specifically.
- -1314 — "Program stopped at statement, line number line." A related message reporting the location of the stop, often accompanying -1315.
- -1316 — "ISAM error number number." A related wrapper-error message, for an ISAM-level error specifically.
A generic 4GL-runtime-error wrapper — look up the embedded error number for the actual diagnostic detail.