I have used NT 4.0 Server for a development environment since it first came on the market a few years ago.

I know this is not advised but, for several years now, when I've finished working and was ready to shut down NT, I simply powered off the PC. I almost never selected START | SHUTDOWN.

I know... I know... this probably makes most people cringe. But I always figured that NT is rock solid. It can take it. And the kicker was ... I NEVER ... EVER experienced a problem or file corruption or any other negative side affect from doing that.

But a couple weeks ago, I swept my PC and installed Win 2000 Server. As my habit was, I just powered off the PC when I was done. But upon going back into various projects I learned quickly that Win 2000 was trashing some of my VFP forms and reports that I had been working on.

Something different is going on with Win 2000 as far as caching writes that wasn't happening with NT 4.0. Keep in mind that I had saved my work and already exited VFP before powering off the machine.

You could say that I should just properly shut down the machine and the problem will go away, but there's more. You see I have been behaving [like a good user] since I noticed this problem and I have been choosing SHUTDOWN. But I blue-screened a day or two ago (because of a video driver) and even though I had exited VFP at least five minutes before the crash, the forms and reports that I had been working on were hosed. When trying to access them in the project manager, I get 'Not a table' error messages or something to that effect. It's only happened with .FRXs and .SCXs. I have not seen a .DBF get hammered.

It's as if the modifications to forms and/or reports are cached (even though I've always cleanly and properly exited VFP) and when I killed NT, it tried to finish/flush the writes to the disk (or something like that).

I can reproduce this on my PC.

Has anybody seen this before? Is there some setting I can change in Win 2000 that will solve this.

And secondly, can anybody else reproduce this problem?

Here's what I've done to reproduce the problem on Win 2000.

1. Close all applications and properly shutdown/reboot the PC.
2. Go into VFP 6.0 (w/service pack 3) and create a new folder and navigate to the new folder (I used MD \test and CD \test).
3. Create a new project
4. Create a new main program with one line of code "DO FORM test." 5. Create a new form called "test" and put a couple controls on it. (I put a label and a textbox on the form.)
6. Save the form and compile the project to an .EXE
7. Exit VFP
8. Power off the PC. (Do not select START | SHUDOWN.)
9. Turn the PC back on and go back into VFP and pull up the project. Is your 'Test' form corrupted?

Thanks for any help or ideas.

Guy