inherited filePro code wierdness

[Mike Schwartz]

     The -j option turns index scan on.       
     
     It's not unusual to see reports on menus that run with dreport.  If the
processing tables are small or if there is no processing run on a report,
there is little or no advantage to tokenizing the code so that the report
can run with rreport.  

     Sort/selection processing can change the data on records.  I believe
you can do just about everything in sort/selection processing that you can
do in regular processing, such as "then:    1=5: WRITE".  However, never
DELETE a record in sort/selection processing.  On page 348 in the 4th
edition of Stuart Werner's filePro Developers manual, there is an
interesting use of sort/selection processing to run "fix" code on a
database.   

Mike Schwartz
    

-----Original Message-----
From: Filepro-list
<filepro-list-bounces+mschw=athenet.net at lists.celestial.com> On Behalf Of
Scott Nelson via Filepro-list
Sent: Monday, September 12, 2022 6:51 PM
To: filePro Mailing List <filepro-list at lists.celestial.com>
Subject: inherited filePro code wierdness

So I inherited a Customer where most of the code was written by the late
former owner of the Company, and there are some odd things that I have never
seen nor done in fP code.

There are many lines in scripts that run /appl/fp/dreport with a -j on the
command line.  I have only used that in clerk processing.  Will that
actually do anything?

Many of the selection processing has copies of the code that is in the
output processing, some writing to files in both.  Does the selection
processing do any writes to files?

Also odd is how most lines that run fP code do dreport instead of rreport
even though it is 4.08 filePro on Unix....



_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
Subscribe/Unsubscribe/Subscription Changes
http://mailman.celestial.com/mailman/listinfo/filepro-list