You do gain something with TABLEVALIDATE set to 0 or 2, just not at USE time. Later, on any attempt to write a (new?) record while the length/count discrepancy exists, an error message WILL be emitted.
>Hi Doru,
>
>VFP8 performs some new validations that require header to be locked, VFP7 doesn't do this kind of validation. If TABLEVALIDATE is set to 0 or 2, VFP8 performs exactly the same validation as VFP7 does. You don't lose anything and don't get anything new.
>
>Thanks,
>Aleksey Tsingauz.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only