another -v processing question

[Kenneth Brody]

(Top-posting corrected, again.)

Dennis Malen wrote:
[...]
>> [...]
>>>>> If there were some way within processing or on the command line to 
>>>>> identify an automatic index to use and -v would recognize this it 
>>>>> would save a tremendous amount of time. Using -v takes longer and 
>>>>> longer as the file grows.
>>>> [...]
>>>>
>>>> I'm not sure I understand what you are asking.  Once this index were 
>>>> specified, are you expecting this to magically tell filePro to 
>>>> access only those records that your processing wants?  All that 
>>>> specifying an automatic index as input does is cause filePro to read 
>>>> the records in index order, rather than record number order.  What 
>>>> functionality are you envisioning here?
>>>>
>>> No, as long as the scan in -v will use the auto index then fine.
>>
>> I still don't understand what you expect to "magically" happen.  What 
>> do you mean by "the scan in -v will use the auto index"?  There is no 
>> "scan in -v".
> 
 > That's the point Ken. I was not able to use the automatic index to speed
 > up the processing.

What, exactly, did you try that "didn't work"?

 > With Nancy's suggested fix, that should make use of
 > the auto index.

Which is exactly what I said in my first reply -- use the "-i" to specify an 
automatic index, and then use lookup-dash on that index to move around in 
the file.

 > My scanning the file required me to start from the beginning and go to
 > the end.

What, exactly, did you do?

 > With Nancy's work around I will now be able to take advantage
 > of the auto index and speed up the selection of records no matter how
 > large the file is.
 >
 > Hope that answers your question.

You still haven't answered the question about what you expected to do that 
would "magically" cause filePro to know which records you wanted.

-- 
Kenneth Brody