Informix Error -50136: In ixSuperTable constructor, neither updateTable nor selectFromPart has been set for this SuperTable, so requested lock mode is invalid -- defaulting lock mode to noLock.

Reasons / Common Causes

-50136 is raised by the ixSuperTable class in the Window Painter GUI builder library — per the official guidance:

You cannot specify a lock mode without also specifying something to lock. If neither an update table nor a table to select from is given, then there is no place to retrieve from, and locking is unnecessary. This error usually results from an omission in the constructor call (you do want to specify locking, but you forgot to name the table) or inadvertently including an unnecessary locking value. Check your code for both of these cases.

1. In ixSuperTable constructor, neither updateTable nor selectFromPart has been set for this SuperTable, so requested lock mode is invalid -- defaulting lock mode to noLock, per the official guidance — the direct, documented condition.

Solutions / Resolution

1. Check the specific value or object state the message names, per the official guidance, against the constraint it describes.

Examples

N/A

No specific triggering statement is documented beyond the class-library condition described above.

Diagnostic Checks

1. Check the specific value, object state, or call sequence that ixSuperTable flags here, against the constraint the official guidance describes.

Related Errors / Related Topics

• -50134 — "Cannot retrieve more than 16382 rows into an ixSuperTable on Windows." Another ixSuperTable-related condition in this set.
• -50128 — "Cannot disable the current SuperField." Another ixSuperTable-related condition in this set.

In ixSuperTable constructor, neither updateTable nor selectFromPart has been set for this SuperTable, so requested lock mode is invalid -- defaulting lock mode to noLock.