a reindex uses index info from the table header. If this is corrupt the only way to fix is the DELETE TAG ALL and create the indexes from scratch using INDEX ON ...TAG... You have to have exclusive use to REINDEX so you may as well go the DELETE TAG ALL route to see if this fixes your problem.

>A simple reindex will correct the index issue. The application is in a multi-user environment and requring exclusive access to the file for adding a location would be difficult. We have a pack and reindex routine that issues a pack and then a reindex on all tables that will bring back any location that has been added and lost. I found another way to get the index back and that is to recompile the database container. The application has gone through many generations and conversions to get the data back to into the new release and the indexes have been created again which does correct the problem then until someone adds a new location and then losses it because the index doesn't get updated. The application and Visual FoxPro doesn't detect that the index is bad giving any error messages.