>Hi All,
>
>I'm tutoring myself w/ VFP6, plan to go to VFP9 later this fall.
>
>As of VFP6 (my release, anyway), indexes created w/ the UNIQUE keyword were still problematical -- i.e., if an indexed record is deleted, the index is not updated to reflect the next undeleted occurrence of the unique value. Has that been fixed since VFP6? If not, what's generally the best way to create a searchable set of unique values from a
>table? Or am I stuck w/ creating a view and then indexing the view?
>
>TIA,
>
>-mark

Check SET DELETED ON/OFF in Help. Also you can create this index FILTERED by NOT DELETED() but in VFP 6 you can't use thios type of index in Rushmore optimization.