Path: utzoo!attcan!uunet!mcvax!cernvax!pan!jw From: jw@pan.UUCP (Jamie Watson) Newsgroups: comp.databases Subject: Re: Informix 4gl - NOT NULL input broken Message-ID: <485@pan.UUCP> Date: 26 Sep 88 23:11:22 GMT References: <476@pan.UUCP> <12609@ncoast.UUCP> Reply-To: jw@pan.UUCP (Jamie Watson) Organization: Adasoft AG, Solothurn, Switzerland Lines: 33 In article <12609@ncoast.UUCP> allbery@ncoast.UUCP (Brandon S. Allbery) writes: >As quoted from <476@pan.UUCP> by jw@pan.UUCP (Jamie Watson): >+--------------- >| 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 >+--------------- > >On what machine, what OS, what version? Vaxstation 2000, Ultrix 2.0, 4gl version 2.10.00A IBM RT/PC, AIX 2.2, 4gl version 2.10.00D Plexus P-20, Sys5.2 release 1.5, 4gl version 2.10.00B Exactly the same symptom on all three. >Your other reported bug also works fine on that combination. Which other reported bug? I've written up *lots* of them lately. If you mean the 'formonly' declaration, you're right; it has already been proven that I misread the manual on that one. Sorry. >(Word to the wise: notify the DBMS company first, *then* the net. You can >get lots of hate mail and/or phone calls from the company if you don't.) I would *love* to. All they have to do is set up a decent support office that I can get in touch with, or set up an email address that I can send bug reports to (and ensure that they will be read and answered), or even convince their U.S. support people to let me call them - I'm willing to pay for the calls!!! Hate mail I can live with. I would also *love* to get a phone call from them, but I am quite sure that they don't want to hear what I have to say. Sigh. jw