Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!apple!claris!ames!lll-tis!lll-ncis!lll-lcc!pyramid!infmx!aland
From: aland@infmx.UUCP (Dr. Scump)
Newsgroups: comp.databases
Subject: Re: Informix 4gl - form input default broken
Summary: prove it
Message-ID: <496@infmx.UUCP>
Date: 6 Oct 88 09:42:56 GMT
References: <473@pan.UUCP> <462@infmx.UUCP> <487@pan.UUCP>
Organization: Informix Software Inc., Menlo Park, CA.
Lines: 36

In article <487@pan.UUCP>, jw@pan.UUCP (Jamie Watson) writes:
| In article <462@infmx.UUCP> aland@infmx.UUCP (Dr. Scump) writes:
| >>      (complaint that I4GL and Perform handle null/blank 
| >>       defaults differently)
| >> 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.
| 

I honestly cannot reproduce this.  The example that I posted did
the functions you described and worked fine for me.  

If you email me your example, I will check it out.

| >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...

THAT figures.  :-]   Seriously though, did you at least *try* my
example on your system?  What were the results?

| 
| jw

-- 
 Alan S. Denney  |  Informix Software, Inc.  |  {pyramid|uunet}!infmx!aland
 Disclaimer: These opinions are mine alone.  If I am caught or killed,
             the secretary will disavow any knowledge of my actions.
 Santos' 4th Law: "Anything worth fighting for is worth fighting *dirty* for"