>>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.


Ed,

Well now, I won't quarrel with the assessment that every machine should have a UPS, and in fact mine do. but that doesn't do a bit of good when the power sqitch on the UPS is vulnerable to being accdentally shut off (the TripLite I have is very vulnerable) or worse, when some driver cause a STOP EXCEPTION and the BSOD, which I have encountered with unsettling regularity. In such a situation, I DO EXPECT a business O/S like Win2K to preserve saved files. I can understand the possibility of damage when the files are open at crash time - although I do not accept that as a given. but I cannot and will not accept such damage to files which haven't been open for several hours or even several days, just because I haven't rebooted. Microsoft has a responsibily to insure the integrity of saved data, and I have the right to demand such.

To comment on your specific suggestions, I have disabled write behind caching, I do have a UPS, and I do use a product which backs up my work automatically. On write behind caching, I will also point out that when a BSOD occurs, and files are damaged beyod repair which are closed and haven't been opened for several hour or even days, caching should not be an issue.

What Francsico has done is to test VFP on Win2K for damage, and he, as well as others here, have found corruption when events occured beyond our control. VSS is one answer, I have chosen a different product because it protects me with each save, not each time I check the file in. And having such a solution is wise. but it should NOT be necesaary just to prevent the O/S from destroying several hours of hard work !!! Your suggestion that I, or anyone else here is negligent in preserving our work is insulting to say the least, and to paraphrase one TV commentator, it is "Most Ridiculous" idea of the day.

Robert Green et al will be hearing about this matter from me, and I hope others at the Miami DevCon in 2 weeks.