Hi Houston,
I've sent the mesage again.
Reading it now, after 1 year, it doesn't seem very clear, but hopefuly it will give you something...
I definitely did not delete the cdx, so I'm not in 'case 1.', but I could be in 'case 2.'. The table is a fox2x table, and I'm pretty sure that after running the REINDEX code, the symptoms of a broken index did not go away, neither on my machine, nor on another 'client'.

>Hi Doru, please try the same Yahoo address again.

>The only problems I'm aware of at the moment are:

1. If you
> - close the table
> - delete the CDX
> - open the table AND ignore the error about the missing CDX
>  (which causes Fox to update the DBF header, to indicate that
>  there is no associated CDX).
> - run the Shared Mode Reindex routine
> - you will get an error because the TagCount() function returns 0.
>
>2. This might be applicable to only Fox2x
> - Changes to the CDX are not detected by 'other clients'.

Regarding:
>
>1. I think this is too contrived to be worth pursuing.
>
>2. I've not attempted to reproduce this. It might be true. It might also be a show stopper - in which case major bummer for me. However it might be curable by having any client including the machine actually doing the reindexing do an update of arbitrary key values causing whatever mechanism fox uses to flag changes to take place. The update would simply replace a key value with the same key value.