> Although, I never had the "not get updated properly" problem (any FoxPro version).

Sorry, I was thinking of IDX files in earlier Foxpro (1.02) versions that did not get updated properly when not open (obviously). I have to admit I have not come across update problems with CDXs.
Sorin


>>It may not be essential under normal circumstances, however the index is a separate CDX file that may get corrupted or even lost or, as I sometimes noticed in earlier version of Foxpro, not get updated properly. That's why IMO the dbase world still cannot afford to release an application without a data maintenance routine that will delete tags and recreate indexes. When to run the maintenance
>
>But I said "As long as everything goes fine"! :) You're right. Although, I never had the "not get updated properly" problem (any FoxPro version). I had a lot of problems in dBase IV, but never in FoxPro (without a reason).
>
>Vlad
>
>> routine, if ever, is hard to say, though, as you wrote Vlad, I would like to hear more opinions about this myself.
>>
>>Sorin
>>
>>>>>A CDX is always open when its table is in use. I noticed that a reindex can speed a little the app when the table is big and it was very much modified.
>>>>>
>>>>But it's not essential at any time, even for Pack/Zap? Maybe just occasional maintenance reindexing on large busy tables will do?
>>>
>>>As long as everything goes fine, I don't see any reason to be essential. But I may be wrong here. I would like to hear more opinions about it.
>>>
>>>Vlad