Informix Error -849

Reasons / Common Causes

-849 fires when a form specification compiles successfully but the compiler reports one or more warnings — per the official guidance, unlike -848's errors, warnings don't have to be fixed before using the form, though it's recommended.

1. A form specification with content that compiles but is questionable (a deprecated construct, a potentially unintended default, or similar) — the general category of condition a compiler warning flags, per the official guidance's framing.

Solutions / Resolution

1. Check the formname.err file, per the official guidance — the same location -848's errors are written to, here containing warning-level messages instead.
2. Review and address the warnings if practical, per the official guidance's recommendation — not required, but advised, since a warning-level issue can still reflect an unintended aspect of the form.
3. Proceed to use the form even without addressing the warnings, per the official guidance — this is explicitly permitted, unlike -848's compilation errors.

Examples

Reading the warning detail file

$ form4gl formname
$ cat formname.err

Diagnostic Checks

1. Read formname.err for the specific warning messages, and assess whether each is worth addressing even though none are strictly required.

Related Errors / Related Topics

• -848 — "Form4gl could not compile Form." A related, more severe compilation outcome — errors that do block successful compilation, versus this error's warnings that don't.
• -832 — "Error found in Form specifications." A related form-compilation error message, for actual errors rather than warnings.

Warnings, not errors — the form still compiled and can be used; review formname.err and address them if practical, per the official recommendation.