×
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.
A couple of considerations regarding load-all and page-at-time subfiles.
Firstly, remember the information loaded in the subfile is a duplicate
of the source data. As time passes, this duplicate will become
increasingly "stale" and no longer represent the accuracy of the
underlying data. Depending on the application, this may not be an issue.
However, if currency/accuracy IS important, then a single-page subfile,
(SFLPAG=SFLSIZ) may be more appropriate.
Secondly, if sensible filtering is in place the User should not be
paging up/down more than a couple of screens-worth. So why load an
entire subfile with 100's of rows? Again, depends on the application and
how much data is involved.
(Since the maximum size of a subfile is only 9,999 rows, I don't think
performance was ever an issue. IMHO, the three different "load
techniques" address different usability criteria - i.e. one size does
not fit all situations.)
HTH,
Brian.
On 17/07/2024 02:30, Reeve wrote:
Single-page subfiles were good back in the days of dreadfully-slow
machines. With today's faster machines, taking an extra second to load a
big subfile which the user can page through quickly appears to be a good
design/resource tradeoff.
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.
midrange.com
