I may be oversimplifying here, but I've been following these threads closely. I've done SOME work under my laptop using Win2K Professional, i haven't upgraded my desktop machine as of yet. I dont use the laptop much because an 800x600 screen just isn't enough. ANyway, it appears this problem happens in VFP and NOT in other apps, and mainly because a modified date does not always get updated by VFP when you rebuild a form. This would be a VFP problem, NOT Win2K. We can debate the merits and dangers of write caching all day, personally, I have my machine on a UPS to prevent crashes and data loss, but that's beside the point. If you save a form, and VFP does not update the modified date, that is a VFP bug, not Win2K. i ALWAYS have to look for the least common denominator in cases like this - if dozens of software packages had file corruption issues under Win2K, I would have to blame Win2K. But sinc eit seems only VFP is afflicted with this problem it is only logical to assume that the culprit is VFP. I don;t much care that it works perfectly if you disable write caching, the fact remains that OTHER packages work just fine with write caching.

Randy