You can do the same with RLA and logical files...

The key is enforce a database independence coding the app.

An RPG program that uses the SQL table to define an external DS to hold the
results of a SELECT * has the same problem as a program that uses RLA
against that same table.

Note: I'm not saying SQL doesn't have benefits or that you shouldn't use
it. Just that you can be lazy and use it wrong just as you can RPG RLA.

Charles


On Mon, Apr 28, 2014 at 11:58 AM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

The funny thing about this to me is how people are always saying there are
no costs to using file I/O and bringing the entire database into the
program. In other words, no database independence.

Just watching this one thread and you have the real costs. Billions spent
dealing with problems like this where we should just be able to increase
the field size and recompile the few programs that use the PO fields which
is what anyone else using SQL on other systems is doing.


On Mon, Apr 28, 2014 at 9:47 AM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

In our Wintouch product, we've occasionally had situations where a
customer needed a longer field for something that's built into the
product.
There, the solution is to simply create a longer version as a
user-defined
field, and then slave the two fields together in the
installation-specific
programs.

Some years ago, in our QuestView product, I found that my predecessors
hadn't provided a big enough field in the internal data structures for
(if
I remember right) the RRN. And simply expanding the field would have
required massive recoding, moving dozens of fields referenced by multiple
programs, with massive potential for errors. So (as I recall) I just
added
a longer version to a place in the structure that was "reserved for
future
expansion," and (again) slaved the two to each other.

--
JHHL

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


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



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.