|
I'm trying not to break too much at once, despite the change from O to prtf. The three fields overlap; does that make sense with regards to your answer? Hey, if I have to change the RPG to make it work, that's fine. I already had to do that for the arrays (thanks to the archives and I think Jon Paris w/ regard to group fields) to make it "the right way". My other choice is to fix the original problem - the fields only overlap because the original designers didn't know whether quantity, price, extended would be the largest field. Thinking through, I should just correct that instead of my original question. Thanks Booth for making me think just a bit more about it! (When modifying vendor packages, I try to change as little as possible, but sometimes it makes sense to second guess them.) -- Sean Porterfield Booth Martin wrote:
I am unaware of any way to show the same field thrice, but to make lemonade from lemons... wouldn't be nice to not worry about indicators? Populate the three fields every time, with blanks if no other value is appropriate? Sean Porterfield wrote:I found an old thread from 2002 that talked about the problem I'm having, but I'm not entirely sure of the solution. I'm making a modification to an RPG program, so I converted from RPG III to RPG IV and decided to move to an external printer file. The mod is a major output change, so it seemed like a good idea at the time. I haven't had much experience with printer files, so I've been learning quite a bit. It seems strange to define all of my fields again, and arrays can't be used. I got through that part, but I have one line that could have the same field in three different places based on other factors. I coded it just like from the O spec with conditioning indicators and the same field in multiple locations. That is where I get the CPD5237 telling me the field has already been used in the record. What? Why on earth can't I use the same field more than once? I can imagine many uses for such a feature. Is there a quick fix that I misunderstood? I don't want to have to define new fields, because I would then have to change the RPG to populate those fields (or create a DS to overlay them). Thanks all! (P.S. The OS will be upgraded "RSN" but this needs to be resolved before that date.) -- Sean Porterfield
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.