×
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.
I don't often disagree with Dennis but I suspect he may be wrong on
this one.
From what the OP said, the program would read each record and then
run the %scan/regex against the record. That means every record would
have to be surfaced in the program. Using SQL it will only surface
those that match the selection criteria - surely that has to be faster
unless a very high percentage of the records are hits.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
On Jul 17, 2010, at 1:00 PM, rpg400-l-request@xxxxxxxxxxxx wrote:
While the SQL suggestion is an option, it is likely to add to your
run time. But (like all performance topics) it depends on what else
is
happening in your code.
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
