sort selection table

[Richard Kreiss]

Dave,

You have a couple of options.

1. Build a demand index on your detail file -
	a. do this prior to running your -v output
	b. build a command line with the sort and system out to dxmaint
	c. Depending on you requirements, system out to dxmaint prior to selecting records or just after the select process completes. (see b. above)

2. Have a cron process rebuild a demand index each night to use with this report

3. Create an output only format in your data file to build your demand index.  You could pass parameters for selection by having a file which holds the selection criteria.  This could be a 1 record file or many records depending on your selection criteria for the primary report.

The tools are there, just not in an obvious way.

Richard Kreiss
GCC Consulting


-----Original Message-----
From: Filepro-list [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Kenneth Brody via Filepro-list
Sent: Tuesday, October 11, 2016 3:19 PM
To: daN baueR <dan at onlinemgt.com>; filePro Mail Group <filepro-list at lists.celestial.com>
Subject: Re: sort selection table

On 10/11/2016 3:09 PM, daN baueR via Filepro-list wrote:
> Just wondering if if this environment is too old for this trick. The 
> OS is AIX with a old version of filePro 4.5. Or is this just not possible?
>
> The report in question was setup in a header file with the body of the 
> report pulling all of the detail lines from another file. This works 
> but the detail lines aren't sorted the way I'd like them to be.
> The V sort/selection table prompts for a single building code and then 
> the report processing uses a loop and a print command to get and all 
> of the data lines.
> I added a sort command to the -v table but it doesn't affect order of 
> the data lines. The print command can't go in the V table. So is it 
> possible to sort the report if all of the data uses dummy variables 
> coded in the output form?
>
> I know I can recreate the report and base it in the detail file. The 
> problem is It's a larger than normal header and I'm trying not to 
> recode the whole thing.

The SORT command will change the output order of the records being selected by the sort/select processing.  However, if the output processing then does a LOOKUP/GETNEXT/PRINT loop to print multiple detail items for each main record, this has nothing to do with the SORT from sort/select.  The records will print in the exact order that you PRINT them.  If you need the detail record printed in a different order, then you'll need to PRINT them in a different order.  Perhaps create an index in that order, and use that index for the LOOKUP?

--
Kenneth Brody
_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
Subscribe/Unsubscribe/Subscription Changes http://mailman.celestial.com/mailman/listinfo/filepro-list
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 11541 bytes
Desc: not available
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20161011/a7a7eb6d/attachment.bin>