Index checking program

[Richard Kreiss]

I have written a routine which will compare the information in the fpidxdat file with a file's map.  A report of all mismatched field sizes is generated.

The report will only point out where a difference occurs.  The decision as to whether this is a mistake that needs correcting or an intentional index length is up to the individual.

Possible reasons for difference:

1.      Fpidxdat not updated after a change in field size

2.      Index for a file missed after adjusting field size

3.      Intentionally using a smaller sort size when building index - (i.e. first 3 characters of a zip code)

4.      Intentionally using a larger sort size (spanning 2 adjacent fields)

Just some of the possible reasons for an error.

I am supplying this program free to anyone interested so please contact me off list.

This is written for a windows system and therefore would need to be renamed to run on a *nix system.

As of now the report generated is using filePro's PDF output option.  This can easily be changed to generate a printed report or even a CSV file.

One caveat, as of now the program does not handle using associated fields.  The program will show that there is an associated field put will not be able to use filedlen(filename,filedNumber) to get the field size from the file.

Richard Kreiss
GCC Consulting
Email: rkreiss at gccconsulting.net<mailto:rkreiss at gccconsulting.net>
Phone: 410-653-2813

I wrote this program as I have been in the process of rewriting a program and making some major changes and wanted to insure that all of the indexed field sizes match.




-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 18703 bytes
Desc: not available
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20170911/c240165f/attachment.bin>