Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Is SP1 resolving the corrupted index problem?
Message
From
10/10/2003 13:43:42
 
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00837119
Message ID:
00837540
Views:
29
>>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.

Hi Sergey,

My point is this - the fact that VFP8 reports an error in this scenario is not a VFP8 bug. The error just exposes an old problem that was there for a long, long time. So, don't kill the messenger. :-) The error wasn't added to VFP8 to address this particular problem, it was added to address a real on-disk index corruptions (that should explain the text of the error message). The in-memory index corruption wasn't known issue until we investigated a couple of cases when the error seemed to be reported false positive and confirmed that this is the case. When the issue is known, it is half way to be fixed.

Thanks,
Aleksey.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform