>Hi Guy,
>
>Just tried it (cringing the whole time). It did not corrupt as far as I can tell. OTOH, wondering why bad things happen when you are not following recommended shutdown procedures is like wondering why it hurts when you bash your foot with a hammer.


I know. This current problem will sure force me to change my habits. But now I'm wondering even more why this is happening to me and not others. I have a typical install with no special services running. Can anybody reproduce this problem?

Until I figured out what was happeing, this had affected a few different projects. Forms or Reports that I had opened but not modified, were OK. But any Form or Report that I made a change to and re-saved got trashed when I shut off Win 2000 in this manner.

In the example I cited in the previous message, I had already exited VFP (for several minutes). It's scary as hell that VFP was closed for several minutes when I got the blue screen which hosed the report I had been working on.

How could this happen? This is only a theory, but it seems that the update to the report had not properly been written to disk even after VFP was closed down.

It occurred to me that maybe the problem was in VFP itself, but I figured that it couldn't be, because I have never encountered a corruption problem when I shutdown properly.

Guy