Oninit
Talk to an expert →

Informix Error -6035: No current row.

Cause and resolution

No current row.

The flag parameter passed to dbfind() implies a current row (for example, a flag of CURRENT or NEXT as opposed to one of FIRST); however, a prior call has not established a current row. Review the program logic to make sure that it establishes a current row before it makes a call of this kind.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-6035 fires when dbfind() is passed a flag implying a current row (CURRENT or NEXT, as opposed to FIRST) but no prior call has established one — per the archived catalogue.

  1. A CURRENT/NEXT-style dbfind() call with no prior call establishing a current row, per the archived catalogue — the direct, only cause.
Solutions / Resolution
  1. Ensure a current row is established before using a CURRENT/NEXT-style flag, per the archived catalogue.
Examples
N/A

No specific triggering statement is documented beyond the function-level condition described above.

Diagnostic Checks
  1. Confirm a prior dbfind() call actually established a current row.
Related Errors / Related Topics
  • -6020 — "There is no current row."
  • -6010 — "Value cannot be found."

A CURRENT/NEXT-style dbfind() call with no row established yet — use FIRST, or establish a row first.