Re: Pros & Cons

["Denis Robitaille" <DRobitaille@xxxxxxxxxxxx>]

I always use different fields. This way if i rechain in the file (for 
validation or whatever) there is no mixup. As for the extra work, there is not 
that much and i can alway use DS to move form PF to DSPF in one instruction. 
The field in the DSPF have the same name as in the PF except that a prefix is 
hadded (the # caracter). This way, in the code, i always know if i am working 
with the foeld from the PF or the DSPF.


Denis Robitaille
Cascades inc.
Tel: 819-363-5187
DRobitaille@cascades.com

>>> Tim-Bar <timbar@blazenet.net> 10/26 7:42 pm >>>
Here's one to toss around -

When creating a display file for a file maintenance program, is it
better to reference the physical file fields or create fields with
different names? If you use different screen field names you have to
move the file fields into those fields to display on the screen and then
move the screen fields back into the file fields before updating the
record format. This seems like a lot of extra work. Is there any reason
to do it this way? 

TIA

Darlene Brengle
Norsoft, Inc.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com 
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---