Informix Error -1314: Program stopped at statement, line number line.

Cause and resolution

Program stopped at statement, line number line.

At the indicated point in the program, an error was detected. Look for other error messages that give details of the error. Use the numbers in this message to locate the error in the program source file.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-1314 fires alongside another error message to report exactly where execution halted — per the official guidance, it names the statement and line number, and directs the reader to look for additional error messages that explain the actual cause of the interruption.

Any underlying error causing program termination, per the official guidance's framing — -1314 itself only reports the location, not the cause.

Solutions / Resolution

Look for additional error messages accompanying -1314, per the official guidance, for the actual cause of the interruption.
Use the reported line number to locate the problematic code in the source file, per the official guidance.

Examples

Reading the accompanying error

1314: Program stopped at statement, line number 42.
1313: SQL statement error -206.
-- the -1313 error on the same or an adjacent line names the actual cause;
-- line 42 in the source file is where it occurred

Diagnostic Checks

Locate line 42 (or the reported line number) in the source file.
Find the accompanying error message for the actual failure reason.

Related Errors / Related Topics

-1313 — "SQL statement error number number." A related wrapper-error message, commonly accompanying -1314 with the actual underlying cause.
-1315 — "4GL run-time error number number." Another related wrapper-error message that may accompany -1314.

A location marker, not a cause by itself — find the accompanying error message and the reported line number in the source.