× 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.



Bob

Yes, I agree with you. But he want to refer same file and twice and want to rename one file's fields. (If I got the question correctly). In this case system will not allow to rename only 2 fields

Then you have to rename all fields with the record format (if both files are having same record format)

I think I'm correct in above scenario.



Regards,

Chamara Withanachchi
Owner of www.rpgiv.info

WWW.RPGIV.INFO
Mob: +971 50 5698644
Tel: +971 6 5595887
chamaraw@xxxxxxxxxx
www.rpgiv.info
i want to be future ready. i want control. i want an i.


Sent from my BlackBerry® wireless device

-----Original Message-----
From: rob@xxxxxxxxx

Date: Mon, 12 Jan 2009 13:16:10
To: RPG programming on the IBM i / System i<rpg400-l@xxxxxxxxxxxx>
Subject: Re: Rename file field in RPGLE


Chamara,

Yes you can. Renaming fields in the I specs was an old trick.

I knew a CASE tool that renamed all 10 character field names down to 6 or
8 using I specs. This was back before RPG supported 10 character field
names. And the tool continues to do so to this day.

I also knew a software vendor that named their fields alike in all files.
For example Order number may be called ORDNO in order header, order detail
and whatever other file used it. If you used order header and order line
in the same program you renamed the fields using I specs (again, before
the days of PREFIX).

Many people still limit themselves to 4 character field names with a two
character prefix, for a total of 6 characters.


Rob Berendt

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.