Re: ATTRIBUTE reverse Turned Off By INPUT ARRAY

Kerry wrote: > > marcog@ctonline.it (Marco Greco) wrote: > > >The input array behaviour seems sensible to me. I suggest you check the > >discussion of OPTIONS INPUT ATTRIBUTE statement, in TFM, to see the order of > >precedence of attributes specifications. > >Our code resembles: > > Marco, > > You are 100% correct!!! The OPTIONS INPUT ATTRIBUTE statement is the > way to go. It can be set once and will work throughout the program. > I must apologized because the FourGen generated code had the > following: > > >CASE > > DISPLAY BY NAME field_name ATTRIBUTE(reverse) WHEN > > FIELDNAME = "field_name" > >END CASE > > And we were "blinded" to just using ATTRIBUTE(reverse) and could not > see the "big picture". > > We are contacting Data Pacific and will let them know that they should > be using OPTIONS INPUT ATTRIBUTE from now on, rather than the above > method which is no longer functional. > > BTW, the information about it being a possible bug that Informix was > looking into was passed on to us by Data Pacific. I am sorry to say > that that information is "suspect" after the above findings. Not necessarily "suspect". We had the same problem upgrading from 4GL-RDS 4.14 on SCO 3.4.2 to 4GL-RDS 4.16 on SCO open server 5. If the behaviour of the control block processing HAS changed, then it means changing hundreds of generated programs for us as well. It would be easier for our clients to wait for the fix, seeing as it is not a terminal error. Cheers, -- Mark. +------------------------------------------------------------------+ |Mark D. Stock - The West Solutions Group http://www.west.co.za | | The Informix FAQ is at http://www.iiug.org | |mailto:marks@west.co.za +-----------------------------------------+ |Tel: +27 11 803 2151 |If it doesn't work, force it! | |Fax: +27 11 803 2189 |If it breaks, it needed replacing anyway!| |Cell: +27 83 250 2325 |Well, that's how I code anyway! | +------------------------+-----------------------------------------+