Re: Fwd: main difference between expandable and singlepage subfile

why anyone would write a more complex page at a time subfile these days is
beyond me.

A "load all" with a filter input field is all that should EVER be needed.

No way a user should be asked to scroll through 9999 subfile rows to get to
the record they are seeking.

Jay

On Sun, Nov 24, 2019 at 4:48 PM Booth Martin <booth@xxxxxxxxxxxx> wrote:

Historically data traveled at much slower rates. IBM needed a means to
get that first screen of data in front of a user asap and thus the
expandable subfile was born. Programmers could push out the first
screen or two of data quickly, and then as the user paged up/down, new
screens could be added as needed. With the ability to add filters and
starting points a user would rarely need to scroll more than a few
screens. All in all a win-win for everyone. Cumbersome for the
programmer, yes, but it saved tons of band width.

With today's speeds and drill-downs the expandable subfile becomes, in
my opinion, anachronistic.

On 11/24/2019 2:09 PM, techie21 IT wrote:

---------- Forwarded message ---------
From: techie21 IT <techiei876@xxxxxxxxx>
Date: Mon, Nov 25, 2019 at 1:35 AM
Subject: main difference between expandable and singlepage subfile
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>


Hi,

What is main difference between expandable and singlepage subfile ?

Thanks

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com