>Something we all should be doing on a regular basis is rebuilding Indexes. Simply relying on the REINDEX command is not necessarily the best route to go. Ideally the Tags should be dropped and recreated from scratch. This is a problem if the Tables are referenced by a DBC and have persistent relationships / Primary Keys / Candidate Keys or if you have systems that really do run 24 by 7.
>
>For a couple of months now some of the FoxPro community’s leading luminaries have had access to a utility I created that facilitates SHARED mode recreation of Indexes. I am now looking to find additional people to put this into their production systems and who are also willing to provide testimonials.
>
>Feel free to reply either to this post or using a private message.
>
>Regards to all,
>Houston.

Count me in on this too!

I have been constantly plagued with index corruption that many users have constantly blamed on bad network cards, cables, this, that and a host of other things without admitting that VFP has a major index corruption problem and it is in the Visual FoxPro software itself! I have even sent a program to Microsoft that builds a table and, using standard VFP syntax, corrupted the index. Single computer - single program which does not even bring in multi-user systems or buffering let alone a 24/7 system with a dozen users. Hopefully Microsoft will wake-up and resolve these index issues soon as they have been a plague since v6 and only getting worse by the release.


Todd