>Just to clear the issue up, the thing that affects the likelihood of any file being damaged is the "window of vulnerability". That window the duration that the file is being written to. Because of how VFP stored memo data, an update usually takes longer than the same update to a dbf file. The longer it takes to update the larger the window of vulnerability and according to statistics the higher the incidence of damage.
>

No question there, and the more layers between the app and the media, the greater the window of vulnerability, as each layer that permits you to defer a physical write and allows you to continue processing introduces some delay in the certainty that the data actually hit the media as expected. And that's how files get corrupted...regardless of type.

The real issue AFAIC is the ability to recover from memo field corruption, and that's an issue of being able to recreate the changes since the last backup was made. And that's the case regardless of file type; it's just that when you break a memo file, the extent of damage is likely to be very large and visible. If you can go to the last backup and reapply the changes in order, the memo fields are no more vulnerable to damage than any other field type.