Heads up on "reindex"....

GCC Consulting gccconsulting at comcast.net
Thu May 3 06:21:49 PDT 2007


 
> 
> In 1985, or sometime way back when, I was using 'dd' to write 
> the headers of indexes to INDEX.A, INDEX.B, etc., and then 
> later copying those files, as needed, to index.? and using 
> dxmaint to rebuild them.
> 
> Later, Marc Parnes and I co-operated in writing two scripts 
> that documented indexes, writing two reports - one in human 
> readable format, and one that could be read by a script that 
> handed info to dxmaint to re-index them.  That was in 1998-2000.
> 
> I don't know what "reindex" script of mine you were using.
> 
> Bob
> 
> PS - The Windows distribution of filePro v5.6 has a filePro program
>      that looks as though it manages index maintenance.
> 
>      From the Windows filePro Main Menu, enter:
> 
>        G => UTIL => T => P => G => UtilIDX
> 
>      and get a menu that looks like an index maintenance menu.  I

Bob is correct.  The index program builds a file with records containing the
command line for rebuilding an index (fpidxdat).
A second program (fpidx) is a process only program which clears the old
data.

The key here is to rebuild the data file as indexes change.  One might need
to set this up as a cron job (at on windows) to keep this file update.

Richard Kreiss
GCC Consulting
 





More information about the Filepro-list mailing list