|
Aaron, if the fields are "input" or "both", than the answer is no. you cannot condition fields on a subfile. if they are output only, then the techniques described by others will do the trick. I agree with you - I have wanted to do the same thing in the past. your other option would be to devise your own paging routines make each line type a seperate record, with a variable starting line number (keyword SLNO?) I wouldn't be easy - you would have to process the page manually, and it would be a hassle, but definately doable. hth, Rick ---original message---- From: "Bartell, Aaron L. (TC)" <ALBartell@taylorcorp.com> To: "'rpg400-l@midrange.com'" <rpg400-l@midrange.com> Subject: Dynamic subfile dilemma Date: Thu, 6 Dec 2001 12:43:41 -0600 Reply-To: rpg400-l@midrange.com I have a problem that I am trying to solve by allowing different fields to be displayed in the subfile based upon another template physical file that I am reading. So basically I want a subfile that can look something like this: Seq Dynamic Fields 999 BBBBBBBBBBBBBBBBBBBBBBBBBBB 999 BBBBBBBBBBBBBBBBBBBBBBBBBBB 999 BBBBBBBBBBBBB BBBBBBBBBBBBBBBBBBBBBBBBBB 999 BBBBBBBBBBBBBBBBBBBBBBBBBBB 999 BBBBBBBBB BBBBBBBBBBBBB BBBBBBBBBBBB 999 BBBBBBBBBBBBBBBBBBBBBBBBBBB 999 BBBBBBBBBBBBBBBBBBBBBBBBBBB 999 BBBBBBBBBBBBBBBBBBBBBBBBBBB I have tried using the non-display character to display the correct field at the correct time but it gives me a field overlap error when I try to add a field that "touches/overlaps" another field. I have tried putting an indicator at the field level for each subfile field but that errors on the compile saying that I can't have a indicator at the field level. But I can have indicators at the field level on a non-subfile field? Hmmm . . . Is there any way to do what I am trying to do? Aaron Bartell
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.