• Subject: Re:Fastest string scan
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Thu, 18 Sep 1997 09:10:26 -0400

>I have an application that display in a subfile a list of all products
>ordered by product number. It shows the product number and the product
>description. The user can request to see only the products that have a
>certain caracter string in their description (Ex: all products with the
>word "ROLLS" in them somewhere). To do that, they type the string to
>look for and the program read the file by product number and, for each,
>scan the description for the string. The string can be anywhere in the
>product description. Currently, i use the SCAN opcode to do the
>scanning. It works great in the test environnement but in production
>(with a lot more products), it is way to slow. I do load the subfile a
>page at a time. I think the delay is due to the SCAN opcode and i am
>thinking of replacing it with the QCLSCAN API. But before going any
>further, i tought i'd ask around. What do you think is the fastest way
>to do this?
>Any help would be apriciated

I've had similar problems in the past.  I've built another file containing
keywords and the key of the record that generated the keyword.
The code was posted in an old News 3X/400 issue - DSPPGMIND
(Display program index)  It's a kludge, but it's one way...

Buck Calabro
Commsoft, Rensselaer, NY

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.