>>That's all right, and when I've read this from Foxpro help (2.x version) I decided never use Unique tags.
>
>Yes, but a SELECT DISTINCT on a 1 gig table is not a beautiful thing where as
>using an existing UNIQUE tag works great when it's correct.
>
>UGH!

I understand this situation. Sometimes (I don't mean exactly your case), the necessity of Unique tag indicates incompletness of database design, i.e. all 'unique' values could be separated into one more lookup table. Here, you could move pointer along primary keys, avoiding 'duplicates'.