×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
It depends on the circumstances. There should not be a
"one-size-fits-all" approach. Ever. Use the right tool for the
particular job you are doing.
For example, if you're doing an output-only list that could potentially
show thousands upon thousands of items, then that'd be an obvious use
for page-at-a-time, but you should also be thinking of the fact that the
user is likely never going to page through that many items, so maybe
it'd be better to offer more filtering.
On the other hand, there are distinct advantages to load-all type
subfiles. For example, you can have a proper scrollbar to use in
scrolling through them -- which isn't possible with page-at-a-time,
because it doesn't know the total size of the subfile, and therefore
can't do a proper scrollbar. As you start moving to GUI tools instead
of 5250 green-screen tools, this becomes more important.
Even if you stick with green-screen only, 1980's style, applications
there are many cases where load-all subfiles work better. They are
easier to write the code for, for example. For entry subfiles (for
example, the user is entering an invoice) they are much, much easier to
deal with because you can have everything stored in the screen. And
there are many applications where you know up-front that you'll never
need more than a few hundred rows, so there's no advantage to using a
page-at-a-time.
-SK
On 4/4/2020 3:34 AM, techie21 IT wrote:
Hi,
Is single page subfile best subfile to avoid limit of number of records to
be displayed?
Thanks
midrange.com
