Running a report without indexes

[Ian Wood]

> >
> > You may not have accessed the corrupted part of the index.
>
> A valid test there, if one were to need one, would be to enter that file
> in dclerk, choose the relevant index, go to browse mode, hit down arrow,
> and then turn on 'C'ontinuous and let it scan the entire file, correct?
>
> (Tip: if you try this, do it in an xterm and hide the window; it will
> run much faster if it doesn't have to do screen refreshes.)
>
> Cheers,
> -- jra
> --
>

I did that, and it ran through all 500,000+ records with no issue.

I'm not expecting a solution as I cannot re-create it, it happens maybe
once every other week, and it can be a different file and different index.

I just think that when running a report that I know is not 'doing' anything
to the indexes, there should be a way to turn off accessing them.
Apparently -ro does not do that, and I'm on the latest and greatest filePro
version now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20130319/9352a0f3/attachment.html