Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!ucsfcgl!cca.ucsf.edu!daedalus!brianc From: brianc@daedalus (Brian Colfer) Newsgroups: comp.databases Subject: Re: Informix 4gl forms - formonly syntax broken Message-ID: <1363@ucsfcca.ucsf.edu> Date: 19 Sep 88 17:18:44 GMT References: <475@pan.UUCP> Sender: root@cca.ucsf.edu Reply-To: brianc@daedalus.UUCP (Brian Colfer) Organization: UCSF Dept. of Lab Med Lines: 42 In article <475@pan.UUCP> jw@pan.UUCP (Jamie Watson) writes: > >The Informix 4gl manual describes use of the 'formonly' field type, with >several associated keywords ("type", "like" and "not null"). However, the >4gl forms compiler *only* accepts the "type" keyword as the first keyword >following the field-name. THis means that it is not possible to declare >formonly fields that are "like" some database field, and it is not possible >to declare formonly fields "not null" without declaring a type for them. > >The examples given in the 4gl manual conveniently do not use any of the >optional keywords in the formonly declaration. Well I tried this effect... The LIKE works fine I think JW's confusion on this is not reading the manual quite carefully enough: fieldtag = FORMONLY.field-name [TYPE [ data-type | LIKE table.column] ] [NOT NULL] [, attributes]; ^ ^ So this works: database test ... f1 = formonly.foo type like test_tbl.col_one; but maybe I'm missing something because this doesn't: database test ... f1 = formonly.foo type like test_tbl.col_one not null; or even database test without null input ... f1 = formonly.foo type like test_tbl.col_one not null; ------ If it is a bug... maybe '.03 release has the fix ... just got it this morning. =============================================================================== Brian : UC San Francisco :...!{ucbvax,uunet}!daedalus.ucsf.edu!brianc Colfer : Dept. of Lab. Medicine : brianc@daedalus.ucsf.edu : PH. 415-476-2325 : BRIANC@UCSFCCA.BITNET ===============================================================================