Re: Field Names -- RPG400-L

Subject: Re: Field Names
From: "Buddy McClean" <Buddy.McClean@xxxxxxxxxxxx>
Date: Fri, 07 Jun 2019 10:30:58 -0500
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@lists.midrange.com?subject=help>
List-id: RPG programming on IBM i <rpg400-l.lists.midrange.com>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

I agree, it would be useful to know.

John Yeung <gallium.arsenide@xxxxxxxxx> 6/7/2019 10:28 AM >>>

On Fri, Jun 7, 2019 at 11:11 AM Buddy McClean
<Buddy.McClean@xxxxxxxxxxxx> wrote:

I was trying to avoid the compare/selects, hoping I was just missing something in a simple statement or 2.

RPG is fundamentally not able to do what you're asking, because of its
statically compiled nature.

In principle, you can do anything in RPG, but in this case, all the
alternatives would be even more complicated than the compare/selects.

You said you didn't know any SQL. Well, now is as good a time as any
to pick some up. Even just rudimentary SQL would be very useful.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.