>>>>Hi Houston,
>>>>On Mon 11/3/2003, I sent you an e-mail showing the result of my testing of your REINDEX, but I did not get any answer from you. Did you miss it, or it didn't deserve an answer?
>>>
>>>Feedback is sufficiently hard to get that I am extremely unlikely to be flippant or tardy in acknowledging a response – so I guess I missed it (or it was blocked by the spam filter), sorry.
>>
>>I replied to the yahoo address from which you sent me the REINDEX code. Do you want me to re-send to the same address, or do you want me to post the reply here? It isn't much, I'm just not sure how you wanted the feedback.
>
>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
> - Somebody reported that changes to a Fox2X 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.