Running a report without indexes

[Ian Wood]

On Thu, Mar 21, 2013 at 11:07 AM, Kenneth Brody <kenbrody at spamcop.net>wrote:

> On 3/19/2013 3:03 PM, Ian Wood wrote:
>
>> Ken,
>>
>> "If you aren't running via an index, and you are not updating any records,
>> and you are not doing any indexed lookups, then filePro shouldn't be
>> accessing the indexes beyond reading the automatic index headers when the
>> file is opened."
>>
>> I get that point that you're making, but the point is filePro IS obviously
>> trying to access those indexes. There are precisely ZERO lookups in the
>> processing table. The command line does NOT contain -i*
>>
>
> I understand what you are saying.  But, you also keep asking if there's a
> way to have filePro ignore indexes.  The answer is no.  Either it needs the
> indexes, because it's using them, or it's already not using them.  (If you
> get my meaning.)
>
> There are very few places where an "invalid index" can be generated, and
> the only one that should ever be even possible in the scenario you describe
> (read-only mode, no lookups) would be if filePro couldn't read the index
> header when the file is first opened, or the "magic number" wasn't valid.
> And, short of transient network errors (assuming the files are stored on a
> network share), neither of those make sense for such an intermittent
> problem.
>
> --
> Kenneth Brody
>

I'm putting this to bed, you've answered that there's no way to bypass,
which I accept.  The exports ran fine Tuesday night and last night.  Not
being able to recreate the issue on demand, makes it impossible to debug.

If it becomes a more persistent issue, Steve Wiltsie gave me a kludge
workaround, I can move the indexes to another location, run the export,
then move the indexes back.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20130321/6d73f3fe/attachment.html