Hi Alexsey, PMFJI but what Doru is asking is very simple. He wants to be able to use TABLEVALIDATE=1 but does not want VFP to report an error if it cannot lock the header.

Currently VFP will report an error if the header cannot be locked assuming there is an error when in fact there might be no error at all - the file could simply be locked by another process.

If the header cannot be locked VFP should not assume an error but instead just abort the test. In this way we get the best of both worlds: validation when validation test is possible otherwise continue without validation.


>Hi Doru,
>
>>>>What I wanted is this: validate the header when you USE the table , BUT, do not trigger an error if the header cannot be locked, IOW do not assume anything if the validation cannot be performed. Wasn't this how things were in FPD/FPW?
>>>>
>
>I believe in your scenario, VFP reports "File is in use ..." error, at least it does it for me. What assumptions are you talking about? VFP doesn't make any assumptions, it can not lock the header, it tells you about it.
>
>>- There is a flaw in the design of this new feature: it triggers an error when the validation was not performed.
>>
>If you have a scenario when VFP reports false corruption error, please, provide a repro.
>
>
>Thanks,
>Aleksey Tsingauz.