>Hi everybody,
>
>I have done some testing on this. And here are my conclusions:
>
>I can consistently repeat the problem in any Win2K Prof. Computer.
>We have the problem since we upgraded the PC's to Win2K.
>
>I repeat it like this:
>Enter VFP6
>in the command window type: Modi Form test
>Drop a textbox in the form
>Press CTRL+W (It's the same whatever method I use to save the form)
>Press the reset button of the computer.
>When Win2k comes back, I enter VFP and the files test.scx/t are trashed.
>

Proving what - if you don't ensure that the write has taken place that the files which may be write cached may be trashed?

Solution - don't do dumb things
Solution - disable write caching for you hard drives
Solution - use SourceSafe and make it a point to check in WIP after modification

I have my systems on UPS boxes, and I have disk caching enabled, but I use SourceSafe, so I can always at least go back to where I started at any point in time. The cost of an adequate UPS (under $100 locally for a ~300-500W unit) is far less than the cost of losing a couple of hours work. Your call, but it makes good sense to me!

DOS Tip - Don't set off a stick of dynamite stuck in your left nostril to clear sinus congestion.

My laptop supports Hibernate, so it's now running 2K and happy as a clam; when the battery drops below a certain level, the system snapshoots the current condition, writes the image to disk, and curls up in a cave. Power On and the system comes back to it's previous state faster than a complete 2K boot. It's also supported on ME.