>>>If using a free table I turn on optimistic table buffering and append blank what happens at that point to the table header? I am asking because I want to know if using buffering makes the table more prone to data corruption. Most of my users are on low end peer to peer networks and I seem to be experiencing much more data corruption since moving to VFP.
>>
>>I didn't notice more data corruption with VFP, than with FoxPro.
>>
>>Be sure to issue a FLUSH after each TableUpdate() - this will not ensure zero corruption, but I think it helps a lot.
>>
>>Hilmar.
>
>Hilmar,
>There is a bug using buffer mode #3 that leads to table corruption. What you want to use is mode #5, but do your TABLEUPDATE after each row change and set the parameters to treat the rows singlely.
>JLK
What! I wasn't aware of such a bug, and I didn't have problems up until now. Or is it that the framework uses mainly table buffering? I'm not sure right now.
Is this bug documented, in some KB article for instance?
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
