>I came across serious problem in VFP 5.0a (same in VFP6.0 prototype version).
>I am using free tables in my application, because some of my old applications share the same data.
>One of table has 8 indexes with primary key. I decided to change one of the indexes, instead of regular I change it type to candidate. Then I tried to reindex. Unfortunately, I had 2 duplicate records ( it can be blank records also) and received error message about violating uniqness. Later, when I checked my indexes (DISP STAT), I've realized that all indexes after index with candidate type were killed. It can be very dangerous when you do not have copy of your table(can be many reasons for that). I think reindex algoritm should be changed by Microsoft. I don't know e-mail address for Microsoft bug fix, I would like to report it to them.
>Any ideas or comments?

Jim,

Don't use REINDEX to recreate the indexes, use INDEX ON ... instead. Then your code won't stop at the first index that fails.