I have a table where it is important that an index tag be correct
at all times that includes the FOR NOT DELETED() UNIQUE criteria.

When a user marks the record for deletion that was being used
by the UNIQUE tag, VFP5a is not substituting another record that
has the same key fields that is not marked for deletion.

Consider the following example where a table with the field TEST has
an index tag: INDEX ON TEST FOR NOT DELETED() UNIQUE TAG TESUNIQ
The table contains the following data in the field TEST:
A
A
B
B
C
C

With the TESTUNIQ tag active you will correctly see:
A
B
C

If you delete the first B record, you will only see
A
C
but you should still see the second B record

This can be fixed by a REINDEX command but this is unaccepable
in a production environment.