INFORMIX Form Spec. File Instructions Problem
Posted in 1991
Path: emory!att!att!cbnewsd!aec From: aec@cbnewsd.att.com (arthur.e.cooper) Newsgroups: comp.databases.informix Keywords: instructions section, control block, if-then-else Message-ID: <1991Oct22.175244.3255@cbnewsd.att.com> Date: 22 Oct 91 17:52:44 GMT Organization: AT&T Bell Laboratories In article <1991Oct15.225646.19765@cbnewsd.att.com> I wrote: > The new section reduces the number of key strokes needed to enter data. > There is a unique set of data that goes with each one of ten codes > entered into a particular field. The (after editadd editupdate of > field-name) control block contains several conditionals. That is, a code > entered into that particular field would cause an appropriate set of > data to populate a set of subsequent fields. When a code not found in > the control block or a NULL entry is made in the field, I want the system > to NOT fill any fields by default. At this point the user should be allowed > to enter the necessary data. But data from the last if-then-else is being > used instead. How can I avoid that? > I tried > if (a6 matches "") then > nextfield = a8 > > as the last condition. It ignored this and pulled data from the previous > condition. I suppose I could put ??? in those fields and let the user > type over but that lacks elegance. > There must be a way to leave things as they are if there is no match. > > Any responses will be appreciated. Although the first few lines of my message were lost you still got the sense of the problem. if (a6 is null) then nextfield = a8 was the way to go. Thanks to everyone who sent suggestions. -- Art Cooper AT&T Bell Laboratories att!ihlpl!wd9aet 708-979-3049