>I'm getting an undocumented error. Clients are running VFP 8 on NT 4.0 sp6 on 1GHz pentiums on an NT/Novell network. The file server is a shared drive on a windows 2K professional PC.
>
>4 PC's are running 5 threads each that do locates on a table. The table has 2 datetime keys and one N(1) key. It has 35000 records. Every night the tables are packed. The keys are populated as records are processed.
>
>I've seen no reference to this error in the VFP help, microsoft.com, UT, or the web.


Hi Hans,

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.

Thanks,
Aleksey.