× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Pete Helgren wrote:
...
And this is where the compiler is complaining. So, if I understand you correctly, the fact that I have a field name that is in two files that have been referenced by EXTNAME, even though the files are different files, causes the error. The EXTNAME on the display file is a convention used in the "model" this program is based on and is required because of logic in the /Copy member that is common to all programs that use this "model".
...

Right, you can't have the same subfield in two unqualified different data structures. There's no problem if you just have the same field in two different files; in that case, RPG happily moves the data to/from either file into that one program field.

... AND so I don't have to explicitly move the data between the screen format and record format...

If Booth's suggestion doesn't help, and you need to have two data structures, and if the database one could be qualified, I think it would work to use a single EVAL-CORR operation to automatically move all the same-name subfields between the two data structures. (You need V5R4 for this.)

The idea of trying to do this with /copy files gives me the shivers, though. It seems to me (probably naively) that it would be better in the long run just to do the required coding in each program.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.