|
Wouldn't it be easier to static code the descriptors onto the screen, then only write the subfile record for those that exist, or one more for each time they add a new one? Example, first time a new guy setup, F6=Add Employment History, writes out a new subfile record for that employment history? Then you could edit check the record to make sure that the data is entered? Ron Power Programmer Information Services City Of St. John's, NL P.O. Box 908 St. John's, NL A1C 5M2 Tel: 709-576-8132 Email: rpower@xxxxxxxxxx Website: http://www.stjohns.ca/ ___________________________________________________________________________ Success is going from failure to failure without a loss of enthusiasm. - Sir Winston Churchill fkany@xxxxxxxxxxxxxxxxxx Sent by: rpg400-l-bounces@xxxxxxxxxxxx 08/12/2004 10:57 AM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To CN=RPG programming on the AS400/O=iSeries <rpg400-l@xxxxxxxxxxxx> cc Subject Re: Assistance with subfile??? For me, the easiest way to duplicate what you're trying to do, is to have one subfile field 70+ positions long and build the subfile field each time it's written. Use some kind of routine to do the following: ================================================== EVAL SFLFIELD = 'EMPLOYER NAME:' + %TRIM(EMPNAME) EVAL SFLRRN = SFLRRN + 1 WRITE SFLRECORD EVAL SFLFIELD = 'ADDRESS:' + %TRIM(EMPADR1) EVAL SFLRRN = SFLRRN + 1 WRITE SFLRECORD EVAL SFLFIELD = 'CITY:' + %TRIM(EMPCITY) EVAL %SUBST(SFLFIELD:50:3) = 'ST:' EVAL %SUBST(SFLFIELD:54:2) = EMPSTATE EVAL SFLRRN = SFLRRN + 1 WRITE SFLRECORD ETC..... =================================================== HTH, Frank "Douglas W. Palme" <dpalme@xxxxxxxxxxxxxxxxxxxxx>@midrange.com on 12/08/2004 08:55:01 AM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx To: RPG programming on the AS400/iSeries <rpg400-l@xxxxxxxxxxxx> cc: Subject: Assistance with subfile??? One of the modules I am working on is for trucking recruiting and I am not sure if it can be implemented the way I have envisioned it. When a truck driver calls us to apply for a job, we of course enter their relevant information into the system, name, address, phone, date of birth, etc. Included in that is their work history for the past ten years. It is the work history that I am having a problem with. We basically get the following information: Employers name, address, city, state, zip, phone, fax, start date, end date, and reason for leaving. I was wanting to display this information in a subfile like the following, with up to two employers per page: EMPLOYER NAME: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ADDRESS: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX CITY: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ST: XX PHONE: XXXXXXXXXX FAX: XXXXXXXXXX START DATE: XXXXXXXX END DATE: XXXXXXXX REASON FOR LEAVING: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX However, when I try to setup the subfile it errors out telling me that I am overlaying the fields, or something like that....so I started thinking that maybe a subfile wasn't the best way to do this.... I am open to suggestions or ideas that someone else may have....it would be nice to see several employers at once. the other thought I had was display the name and dates of empoyment in a subfile and allow the recruiter to select an entry to drill down to the detail...but since I have never done selections within a subfile that might be getting beyond my abilities. Douglas -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.