I would like to take a poll regarding the file system in use on the drive where this problem occurs? FAT32? NTFS?

It sounds like there might be some long-persistence file buffering at the OS level that's causing the problem... not an inherent VFP problem.

Any comments from the Win2K admin gurus out there who might know how to tweak the OS so this doesn't happpen?


>Hey All,
>
>Wanted to report something I've been experiencing and see if anyone else has seen this:
>
>I run my laptop on Windows 2000 Professional. Lately, I've been on an extended business trip where frequent small modifications to a rather large VFP application are needed.
>
>The other night, I was working really, really late and, being groggy, turned off the computer without a clean shutdown. Now VFP was up but the project file had been closed. Still, when I cold started the next morning, several SCT, SCX, and FPT files were trashed.
>
>Friday, I was in the middle of a debug. I went to lunch with the debugger up in the middle of an app. Some idiot PC tech came in and unplugged my laptop while I was out. My battery was low so at some point it shut itself down before I got back. When I restarted, yes, several SCTs and one FPT were corrupted.
>
>So, in my experience, Windows 2000 seems to be much, much more prone to corrupting VFP files in "oops" situations than any other Win operating system.
>
>Does anyone have any similar experiences and, if so, besides the obvious answer of always ensuring a clean shutdown, did anything ameliorate the sensitivity?
>
>Thanks.