× 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:
...
a) Extname - Causes a RNF3804 error on the fields that are in the screen format that have the same name as the data structure or file (I think...the error is pretty vague:"Name Field1 in external description PMYFile is not renamed external name is ignored.")
...

Are you coding EXTNAME for the screen file or the database file? Since you have the same field names in both files, you can only define an EXTNAME DS for one of them (unless you use PREFIX or QUALIFIED for one of them which defeats your current purpose).

I think you want to compare the old database record with the new database record, so you should code an EXTNAME DS for the database file. When you READ the database file, it would automatically populate the DS. When you EXFMT your screen, any output-capable screen fields that have the same names as the database file would be set from the DS, and any input-capable screen fields would set the DS fields after the EXFMT.

If you only have one EXTNAME ds, then you'll have to hunt through the listing to find out what's up with the RNF3804. For one of the subfields you are getting the error for, look in the cross reference to find out where else that field name has been defined earlier in the program. Maybe you have them defined in another data structure. Be sure to use the listing for this; you can't always tell what's going on from your original source.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.