Sort/Selection processing

[John Esak]

Yes, I realized right away that @ts wouldn't have a meaning other than Total
Records Processed, not Total Records Selected.  I think it *would* be useful
in this context.  Not *real* useful... But somewhat, maybe... Sometimes...
Perhaps. Oh, okay, it's pretty much not to useful a thing to know, other
than to just know it? Since it has no relation to how many you actually
select, you couldn't use it for much of anything.

John



> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at spamcop.net] 
> Sent: Tuesday, June 15, 2010 3:49 PM
> To: john at valar.com
> Cc: filepro-list at lists.celestial.com
> Subject: Re: Sort/Selection processing
> 
> On 6/15/2010 2:12 PM, John Esak wrote:
> [...]
> > I will assume that @ts has no value either on the -v table. 
> Although, who
> > knows (besides Ken :-) maybe it does. In which case, you 
> could set an
> > incrmenting counter for every record encoutnerd selected or 
> not and when @ts
> > equalled this counter, you'd be done with the -v processing.
> [...]
> 
> I'd have to check is @TS has any value during sort/select 
> processing.  But, 
> even if it did, what would it mean?
> 
> Consider this:
> 
> I hand you my Rolodex, and ask you to pull out all the 
> clients from New 
> York.  Part-way through, I ask you "how many New York clients 
> are in my 
> Rolodex, and have you gotten all of them yet?"
> 
> -- 
> Kenneth Brody
>