Re: Field Reference File

[rob@xxxxxxxxx]

Yes, stop using unique field names.  There's no reason that the item 
number needs to be called ITNBR in your item master file and ORDITEM in 
your order file.  I'm not assuming what language you do, but RPGLE allows:
     D ItemMastDs    e ds                  extname(ITEMMAST) QUALIFIED
     D OrdLineDs     e ds                  extname(ORDLINE) QUALIFIED
     C/FREE
       chain(e) (wOrdHead: wOrdline) OrdLine OrdLineDS;
       chain(e) (OrdLineDs.ItemNbr) ItemMast ItemMastDS;
       OrdLineDS.Desc=ItemMastDS.Desc;
       Update(e) OrdLine OrdLineDS;

At least in V5R2.

There's a host of benefits to not using unique field names and very few 
reasons to use unique field names.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




Colin Williams <colin.williams@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces+rob=dekko.com@xxxxxxxxxxxx
10/27/2003 12:25 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
Field Reference File






Guys,

We use a field reference file to hold every field in every file in our 
main
application, so that we have unique file names across our app.

Unfortunately we have reached the maximum record length for a file, so can
no longer add fields to our current field reference file. 

Can anyone think of a way to overcome this problem, and does anyone know 
if
the maximum record length increased
in V5R2

Cheers
Colin.W
For the latest on Bertram Books products and services and for 
up-to-the-minute book news visit www.bertrams.com


This e-mail and any attachments may contain information that is 
confidential and privileged and is solely for the use of the intended 
recipient. If you are not the intended recipient please notify the sender 
and delete this e-mail and any attachments immediately






_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.