|
Well, thanks again to all for the new answers. Martin, thanks for the link to your code to CRTCSVDTA. I'm studying it and will try the reverse way. Douglas, you are right, reading all other suggestions I missed Charles quote when I wrote that nobody had answered my original question. Anyway, I had searched through the archives first, before posting the original question and hadn't found any thing... (although he said: "This has been discussed numerous times in the archives") Well I could not find it. Rich, thanks for your comments. I had thought of doing it that way, and it's precisely for avoiding it that I asked if it could be done some other way... I think I have it quite more clear now. Thanks to all again. Martin Rowe escribio': >On Saturday 12 June 2004 18:22, afvaiv wrote: >[snip] > > >>So, let me present again my original question: >> >>If, in a RPG pgm, I manage to have in a field (let's call it FieldName) >>the name of a real field from an externally described file, and in >>another field, call it "FieldValue", a value (either alfa or numeric), >>is there a way to write something as: >>Eval FieldName(??) = FieldValue >> >> > >Antonio > >Have a look at the code behind CRTCSVDTA, one of my open source utilities. >That dynamically processes fields from a file by reading from a program >described file and extracting data from the record based on info from the >list fields API. It should be do-able to reverse the process and write to >a file using arrays to hold the field names and values. The RPGLE code >can be seen here: >http://dbg400.homeip.net/cgi-bin/viewcvs.cgi/dbg400/QRPGLESRC/DBG201R4.rpgle?view=markup >and the whole utility from http://www.dbg400.net/crtcsv.html > >Whether it's any quicker or not is debateable, but I think it is feasible. > >Regards, Martin > > -- Antonio Fernandez-Vicenti afvaiv@xxxxxxxxxx
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.