|
(Original reference: Problem with sub-file display) Thank you very much for your time & all the answers cocerning my sub-file displaying only blank records. The problem is now solved: I was specifying the SFLINZ keyword unconditionally in my DDS... In fact, my ultimate aim was to create a generic pgm that can be called from within any interactive pgm (with the appropriate parms, like file name, field names), that would display the specified file onscreen and enable selection of a record, returning back the key of the selected record to the calling pgm. I am sure some of you have already tried doing something similar so maybe if anyone is interested we could start a discussion thread on this.I would be glad to get your suggestions. Let's work within the following parameters: 0. This program is to be callable within any other interactive pgm and is to display some selected fields from a file, together with an option field to select a record. On user input, it returns back the key of the record selected in some specific positions in the LDA. The calling pgm has to specify which file & which fields are to be displayed and it must only be 'aware' where the subfile is being displayed 1. We do not know in advance the name of the file and of the fields that need to be displayed. (This is of course the objective of having a generic pgm & screen) 2. The number of fields to be displayed can be variable (but obviously must be limited. For our purpose let's assume up to a maximum of 10 fields can be displayed). Fields can either be numeric or alphanumeric. 3. Field name & file names can be passed to the pgm either as parameters or in the LDA. 4. The subfile display would have only 2 fields: say WSEL & WLINE. WSEL is a 1-char i/o field that can accept an input (e.g 1:Select 2:Modify 4:Delete etc...) The calling pgm then would receive a) the user input and b) the record key and do whatever appropriate with it. WLINE would be a ,say, 70 char field that would be used to display the required fields. 5. Use only SQL statements to read the file. 6. Avoid using any API 7. Only RPG4 to be used (not RPGILE) 8. The less instruction lines the pgm can contain, the better (I'm dreaming I know...) So questions to you experienced RPG4 programmers :Is this objective attainable? We can eventually make this 'open source' i.e as soon as we get something workable we can publish it to this list(with your permission). Your suggestions are welcome. Thanks ------------------------------------------------------- Original mail : >Hi all, > I have just started programming subfiles (using RPG IV)and I am getting a little problem: The pgm writes some information to the subfile records >e.g C* write something to a field of the subfile record C movel 'XXXX' sfld1 C* write the subfile record C write SFL C* The above 2 instructions are repeated a few times C* just to fill a few subfile records C* C* read/write the subfile ctl C* write SFLCTL However the screen displays a blank subfile : |------------------------------------| | | | --- ------------- | | --- ------------- | | --- ------------- | | --- ------------- | | --- ------------- | | --- ------------- | | --- ------------- | | | |------------------------------------| >I am sure that there is something obvious (to all of you experienced RPG programmers) that I am missing but I have been battling with this simple problem for almost 1 day without success. Any help please? >TIA __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.