Re: Puzzling forms

Hi Peter. Having sideways scrolling in no problem, just define your form in the next way: f1 f1 f1 f1 f1 f2 f2 f2 f2 f2 f3 f3 f3 f3 f4 f5 f5 f5 f5 f5 .. .. .. .. .. f24 f24 f24 f24 f24 SCREEN RECORD a_s[5] ( f1 , f2 , f3 , f5 .. f24 ) Of course you are still limited horizontal )max 80 columns) and vertical )24 rows) but it gives a lot more space to show fields. be aware that the cursor keys still work as normal, so arrow up is left column, arrow down is right column. If you cannot work it out, I can send you a copy of an existing solution. Good luck Henk Sanders hjs@worldonline.nl Peter Lancashire wrote: > > Jorgen Lehmann wrote: > > > > Hi Peter, > > > > Thanks for your answer, which does confuse me a bit however: > > > > >Yes, I have done this sort of thing. Basically, you use the BEFORE ROW > > >clause of the INPUT ARRAY statement to call the routine that displays > > >the field_3 and field_4. It needs to know the program array index of the > > >current row, which can be had from function ARR_CURR(). It then does a > > >DISPLAY from the appropriate record of the program array. > > > > Somewhere I get the feeling, that I've been reading the manual, like the > > devil reads the bible, as I'm using DISPLAY ARRAY, to show the collected > > information (using a cursor) - This statement don't seem to like the > > BEFORE ROW, so I'm a bit stuck here... When do I use the INPUT ARRAY, > > instead of, or after the DISPLAY ARRAY statement ?? > Use INPUT ARRAY if you want to manipulate the data or do anything > really. DISPLAY ARRAY doesn't use the BEFORE and AFTER events so it > actually is pretty useless, as Nils says. If you're still stuck I could > dump a bit of my code here for you to look at. > > > > >INPUT ARRAYS that are too wide for the screen must be one of the biggest > > >bugbears of 4GL programs. A fix for this (sideways scrolling, perhaps?) > > >must be at or near the top of most folk's wish list. > > > > Well, I certainly would have been pleased to see an example or explanation > > in the manuals. Would have made life a bit easier, as I'm stuck with a > > record layout of 2*30 char's description plus pricing, unit, stocknumber > > etc etc.. ;-( > Have you read Informix 4GL by Example? It seems to come with the manuals > these days. It's quite good for getting an understanding of what 4GL > code will (and won't) do. > > > > Regards, > > > > Jorgen Lehmann > > Systemansvarlig > > > > jll@nst.dk > > ---------- > Good luck. Peter > -- > Peter Lancashire > Information Systems Specialist, Bayer plc > Eastern Way, Bury St Edmunds, Suffolk, IP32 7AH, UK > Tel: +44-1635-562258, Fax: +44-1635-562281 > Mail: Peter.Lancashire.PL1@bayer.co.uk > --- > My Internet plumbing does not allow me to mail and post news together. > Sorry. > All opinions are my own and not those of Bayer plc. > --- > Join Infuse, the UK Informix User Group at http://www.infuse.org.uk/