I-4GL 4.10 Input Array Annoyance

One of the most annoying features of the 4GL input array statement occurs when the database has columns defined as not null and the user hits ESCAPE on an empty line. Rather than realizing that the line is empty, the program demands that the user enter something into the field. There are several workarounds that I am aware of, all of which require defining another key which will exit input. This is horribly tedious. This also occurs in a situation where the key elements of the row are scanned, and then lookups occur to display the rest of the info for the scanned item before moving the next row for the next scan. If the user wishes to move up and rescan the previous item or change something, 4GL blithely informs them that such and such a field requires input. This is an even worse case of we-know-better-than-you from Informix. Anyone know of an input array option which will eliminate this? Could this be a function of using version 4 4GL with a level 5 database engine (Online)? I can't even find this feature in the manual. Please keep me from letter-bombing Informix :-)? Thanks. Mike Lemon