>Hi Sergey,
>
>Keep in mind that VFP7 and earlier versions have the same problem with index (when SET REFRESH setting is to big, the cached part of the index can become so outdated that it doesn't match the table and can not be safely connected to the rest of the index), but don't report an error. Is it what you really want?

Hi Aleksey,

You don't expect me to answer this question, do you? :)
I belive that current VFP8SP1 behavior still a bug because VFP reports index corruption in case where there is none. It should be handled by VFP internaly by discarding current read buffers and reading indexes from a disk or some other way. Right now there's no reliable way to prevent this bogus error from happening besides maybe putting SYS(1104) before any VFP command that can use indexes.