The corrupt index can be caused by several things. There is a KB article on my website that explains some of the common problems and what you can do about them. However, the first rule is...don't reboot in the middle of the application!

Table size shouldn't be a problem. I've dealt with a 1.7 Gig table holding 11 million records without problems.


>Hi to all,
>
>very strange problem, I've an app on a lan (50 user) that it has some big table ( the biggest have 350.000 record for a total size of 100MB)
>Each night we pack and reindex all table ( reindex with sotnefield tools).
>
>Sometimes happens that when the user is saving the Pc crash ( not GPF but the VFP app don't give any sign) so the users have to reboot the PC. Not always but sometimes this operation corrupts the indexes.
>Have anyone worked with this problem ?
>
>Another strange problem it's that indexes are corrupted after the launch time, maybe because users don't close app and table remain opened and PC go in stand-by. Can the stand-by a real problem for the indexes ?
>
>Does you work with big table, or can be the size of table the real problem ? the most corrupted is the biggest table, but it's also the most used table ( it's the detail of orders ).
>
>TIA for any suggestion
>Renato