RE: Field interpreted differentlybetweenphysicalandlogical

Barbara,

I think I see what you are saying.  Adding the extra DS seems like
duplication and I wonder if it might be confusing later to someone
coming behind me.

On a side note to your previous post.  I used to use unnamed DSs until I
started using WDSc.  I found that having several unnamed structures in
the outline view makes it difficult to find things.  It's much easier to
give them some kind of name so they can be identified when I'm trying to
locate where subfields and things are being used.  With long names
available now it isn't difficult to make it different but still
meaningful.

Rick

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
> Sent: Tuesday, March 14, 2006 7:14 PM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: Re: Field interpreted differentlybetweenphysicalandlogical
>
> Rick.Chevalier@xxxxxxxxxxxxxxx wrote:
> >
> > I'm beginning to question whether this really is a good
> idea.  Due to
> > deadlines I coded around the issue by moving the database
> fields into
> > the DS fields prior to the call.  The CONST solution sounds like it
> > might work better.  I'll have to try it when I get the chance.
> >
>
> Rick, using CONST is indeed a very good idea.  But I think it
> would still be useful for you to see how defining the
> externally-described DS in your main source file would also
> fix up the problem.
>
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L)
> mailing list To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>
>

Privileged and Confidential.  This e-mail, and any attachments there to, is 
intended only for use by the addressee(s) named herein and may contain 
privileged or confidential information.  If you have received this e-mail in 
error, please notify me immediately by a return e-mail and delete this e-mail.  
You are hereby notified that any dissemination, distribution or copying of this 
e-mail and/or any attachments thereto, is strictly prohibited.