×
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.
Why do a position-to when sql offers "like" so you can easily use
wildcard filters to provide human-scale load-all subfiles, even with
huge files?
Specifically _because_ underlying PF data may change you, as the
designer, can build in frequent refreshes so that users don't page
around in hours-old data.
Load-all subfile programs are around 200 lines of code, easy to reuse.
(I have a 2-column load-all subfile program with 235 lines. It includes
wildcard filtering on either or both columns, and either column may be
sorted in ascending or descending order. 235 lines including headings
and comments.
On 12/30/2019 8:56 AM, Patrik Schindler wrote:
Because doing position-to in a load-all is cumbersome.
Because data in the underlying PF can change and completely reloading even so often seems to me a waste of resources.
Because if you have one paged-SFL coded properly, it's relatively easy to reuse that code for another SFL.
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.
midrange.com
