SNIP>
>This error can be reported if the index is really corrupted or the part of the index that is already loaded into memory doesn't match the current index state (significant modifications have been made to the index by other clients). When VFP tries to load the rest of the index, new and old parts don't match and VFP8 reports the error. VFP7 and prior versions don't perform this kind of validation and don't report the error, however, this in-memory index corruption can have severe consequences on fast computers.
>
>To avoid the in-memory index corruption try to do any of the following (alone or in combination):
>1) SET REFRESH to as less value as possible.
>2) Decrease buffers size using SYS(3050)
>3) Lock the file before index read operation. File lock discards all buffers for the table and its indexes the same way SET REFRESH does. Then you have a choice to unlock the table right away or after the read operation is completed.

Aleksey,

Thanks for a great explanation.
I just want to clarify something... I *assume* that the buffers you are referring to here are VFP internal buffers maintained in VFP storage and managed by VFP. Is that correct?

If it is correct then I suspect that a low value for the REFRESH parameter(s) may have minimal actual performance consequence, on the basis that the OS is itself separately maintaining its cache and that changed CDX (or any other) records might well have been updated in the OS cache and so really come to VFP directly from there. Do you think this is aplicable?

cheers

>
>Thanks,
>Aleksey.