Path: utzoo!attcan!uunet!mcvax!cernvax!pan!jw
From: jw@pan.UUCP (Jamie Watson)
Newsgroups: comp.databases
Subject: Informix 4gl - NOT NULL input broken
Message-ID: <476@pan.UUCP>
Date: 16 Sep 88 09:49:35 GMT
Reply-To: jw@pan.UUCP (Jamie Watson)
Organization: Adasoft AG, Solothurn, Switzerland
Lines: 18


The NOT NULL input specification is completely broken in Informix 4gl when
used in an "input array" statement.  It is supposed to be possible to specify
this several ways, including as an attribute on a database field and as a
specific keyword to a formonly field.  Both declarations suffer from the same
problem.

When giving input to a field that is declared "not null", press ctrl-d
to clear the current contents of the field.  Then press RETURN to move to
the next field.  You get a message that says this field requires a value
to be entered.  Then just press RETURN again.  The cursor moves to the
next field.  You will never be bothered about that field again, and the
value that is returned to the 4gl program is NULL.

This seems to work correctly when using an "input" instead of "input array"
statement.

jw