|
I've done something like this years ago using a single subfile and multiple occurrence data structures. If I remember right, it wasn't really that difficult to do, just takes a bit to get it straight in your own mind at what level the data for each side of the subfile is stored in with each mods. But it's not too terribly complex. -----Original Message----- From: midrange-l-bounces+ldalton=turbogorilla-software.com@xxxxxxxxxxxx [mailto:midrange-l-bounces+ldalton=turbogorilla-software.com@xxxxxxxxxxxx] On Behalf Of Wilt, Charles Sent: Tuesday, May 30, 2006 1:59 PM To: Midrange Systems Technical Discussion Subject: How to have multiple views of subfile data? All, I've gotten a request to put together a subfile program that allows the user to choose between two different views of the data. In one view, each subfile record takes two lines. In the other, each subfile record takes 3 lines. Note that while about 75% of the fields are the same between the views, all the fields on line two of one view don't show up at all on the other view. Kind of like the different "views" IBM provides in the WRKSPLF command for example. I've never had a request like this before, in the past I've always made use of SFLDROP/SFLFOLD. I thought I'd see if anyone had run into this type of request and how you handled it. I've considered having multiple subfiles defined in the DDS. Or perhaps using a single subfile with just one long text field. Unless I'm mistaken, with either of those techniques, it would be easiest to use a page at a time subfile so that I could show the same screen back to the user when they switched views. Perhaps DDS is not the right tool for this request and I should use UIM. Thoughts anyone? Thanks, Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121
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.