>I never used FLUSH in years. I tried it yesterday for a new approach but I dropped it today when I changed the lock to be at the related table level. So, I never exactly tried to know how VFP in the back is dropping the data to disk. My assumption is that was normally instantly. But, we've seen at high traffic that this is not usually the case if you have multiple apps querying the table at the same time.
My understanding is that a TableUpdate() does not provide an implicit FLUSH, either. So, the risk of data corruption does exist, especially if there is a temporary problem with the power, or the network connection.
I considered this important enough to modify the third-party framework, to provide a FLUSH after each TableUpdate() (fortunately, I only had to do this in a single place).
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)
