>>>>What are the factors that can make an index fall out of step with its table, Can network etc cause this ?
>>>
>>>Mark,
>>>What do you mean "fall out of step"? What type of symptoms are you having?
>>>
>>>-Ed
>>>
>>> Its Foxprox 2.6 , We had a power cut last monday, since then all Fox Dos processes have been running slow (very) some files are not reading at all & it seems the master table's index is not updating with the table
>
>Index corruptions happen quite a bit with Fox 2.x. Since you had a power cut, this is probably what is wrong. You are going to have to close your tables, open them exclusively and run REINDEX on each of your tables. This should fix it. Good Luck.
>
>-Ed

It happens quite often that a simple REINDEX won't do the trick. It is a good idea to stay away from the the REINDEX command to rebuild corrupt indexes because REINDEX uses the index header information to perform the indexes. If the header of the file is corrupted, the new index will be corrupt also. The solution is to delete the .cdx file and create all of the indexes from scratch in the table designer. If you find this tedious, many people write short procedures that programmatically rebuild all of their indexes for them. Then you can just run the program instead of doing it manually every time. Even better are products which use a data dictionary to automatically reconstruct all of the indexes for every table in the .dbc. I use Stonefield's database toolkit, which has a lot of other cool features, but we purchased almost exclusively for this reason. It has a method that can be called from your app that allows a user to perform the reindexing (and another for repairs). This way, when a user's system crashes, they can run the epair and reindex utilities themselves.