Re: Puzzling forms
Posted in 1998
Topics: Stored Procedures & SPL, Connectivity: ESQL/C, 4GL & Embedded SQL
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 ?? >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.. ;-( Regards, Jorgen Lehmann Systemansvarlig jll@nst.dk ----------