>I seriously doubt that VFP could do that.
>The OS, on the other hand, might be a good candidate, especially if write cache is enabled (workstation or server) or OPLocking is active, an intermittent RAM problem and such.

My guess is also more on the hardware / os side of things. For instance I found data errors at an installation where they had exchanged some disks on older machines. Some of them were beyond 120 GB, and the registry key EnableBigLBA was not set - they encountered data errors sometime soon. Usually the fox throws errors, albeit sometimes with error messages leading you directly elsewhere <g>. Here I think some file pointers were screwed up royally, which might also point to RAM and or CPU.


my 0.02 EUR

thomas