>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.
>

Yes, after the "Attempting to lock..." (which can be an endless loop if SET REPROCESS = 0), VFP reports an error. FYI, in a multiuser environment, the fact that a file is in use by another is a normal event, not an error. If the file was in exclusive use, then I'd agree, but it is not the case. You should be able to open a locked file, you just cannot make any change to it.

The assumption is this: if the header cannot be locked, TABLEVALIDATE reports an error - this is, without any validation being performed.


>>- 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.

If you read the above again, I didn't say that VFP reports false corruption. Why are you trying to complicate a very simple thing?

>
>




>Thanks,
>Aleksey Tsingauz.