Yup, use that one too. The only point I'm making is that there is still a use for it if only for the sake of us old farts who have been using it for analysis for many years :-)

>True, but SELECT DISTINCT does the same thing. And, you can easily add a COUNT() column to see how many of each value exists in the table.
>
>>Josh ---
>>
>>You are correct, however I have found Unique indexes to be invaluable when developing. A lot of my work involves redesigning databases and migrating legacy tables into VFP. When I go to normalize a column, I create a temporary compact unique IDX to see the range of values I have to be concerned with ... I just couldn't do that with a Candidate key (even if I wanted to create a CDX)
>>
>>>
>>>That's true, but a unique index is not the same as a candidate index. It doesn't keep you from adding duplicate values, it just ensures that only one record will appear in the index for each distinct key value.
>>>
>>>>Rock ---
>>>>
>>>>Yes, it's still needed. If you are creating a standalone index (IDX), Candidate is not an option.
>>>>