Path: utzoo!attcan!uunet!mcvax!cernvax!pan!jw
From: jw@pan.UUCP (Jamie Watson)
Newsgroups: comp.databases
Subject: Re: Informix 4gl - form input default broken
Message-ID: <487@pan.UUCP>
Date: 29 Sep 88 23:01:25 GMT
References: <473@pan.UUCP> <462@infmx.UUCP>
Reply-To: jw@pan.UUCP (Jamie Watson)
Organization: Adasoft AG, Solothurn, Switzerland
Lines: 29

In article <462@infmx.UUCP> aland@infmx.UUCP (Dr. Scump) writes:
>> Using the *identical* form with the Informix-SQL Perform form processor
>> everything works correctly.
>
>Not true. [E1]  SPERFORM and 4GL hold the same rules.

Well, I have a form here that can be run with 4gl, and fails, and can
be run with SQL, and works.  It would appear that regardless of whether
Informix *thinks* or *claims* they "hold the same rules", they don't.

>> In fact what is apparently happening is that the field is getting a null
                                                          ^^^^^^^^^^^^^^^^^
>> value by default, instead of a space, because adding null to the include
   ^^^^^^^^^^^^^^^^
>> list causes the form to accept the default value under 4gl.
>
>Also not true. [E2]  The default of <space> is not "being accepted";
>the input variable value is NULL, not space.  By adding NULL to the
>INCLUDE list you are allowing the NULL to come through.

Which is *EXACTLY* what I said was happening.

>Try the
>following sample:  (sorry for the bandwidth, but I felt an example 
>was important to reduce disinformation):

So far, I haven't seen *any* "disinformation" in MY posting...

jw