fpidxdat

[Richard Kreiss]

As most of you know, fptech has supplied a program which will build a command file, fpidxdat which holds the commands to rebuild all of your automatic indexes.  

A batch file, fpreindx.bat is created with the windows version.

I am not sure if any of you have carefully examined the resulting batch file.  This evening I needed to delete the 5 auto indexes for one file on a clients server and rebuild  them.  I ran the fpidx program to create the file. When I double checked the batch file created, I noticed that  some of the command lines were incomplete as the command occupied more than the 60 characters allocated in fpidxdat.

I have indexes on this system which are qualified and use 6 sort fields.

                                    TOOLSIDX
────────────────────────────────────────────────────────────────────────────────

Command Line:
60 character field
dxmaint l_patient_market -RF 14,4,a:20,14,a:1,20,a:2,20,a:11◄

80 character field
dxmaint l_patient_market -RF 14,4,a:20,14,a:1,20,a:2,20,a:11,10,a -oM -E -m ""◄

I increased the field size to 80 characters and reran fpidx.  I check the fpidxdat again and the command lines for all of the files/indexes were complete.  Based on this run, I may need to increase this field to 100 characters.

My suggestion if you are using this program as a method of insuring that you can quickly rebuild all of a programs automatic indexes, that you check either the batch file or  the fpidxdat file to insure that the command line is complete for each index.

If you have not tried this program or are not using it, you are missing a great tool for maintaining a quick method for rebuilding indexes.


Richard Kreiss
GCC Consulting
rkreiss at gccconsulting.net