Hi,
Yes I have seen the same thing happen at low loads, but it is a waste of time saying that it happens, as the EXPERTS say it can't, so they must be right.

>>Hi,
>> I have seen MS Word cause delayed write failures on highly loaded networks when disk caching is turned on.
>
>I've seen it do it on a very (very) low loaded network, even to the E: drive (local, my data only) drive. In fact I'd say it happens with 48hrs of my getting/using a new mahine, thus reminding me that I've forgotten to turn off write behind caching.
>
>cheers
>
>
>>
>>>>>I've noticed this trend years ago - all sorts of network problems were detected in Fox apps only, because we were the only ones who were seriously stressing the network. Nobody noticed when a .doc file loaded a few seconds slower, but everyone sees when a popup/lookup/dropdown/whatever takes three seconds longer than usual. And when the network guy comes, he'd just save another Word doc to show everything works ;).
>>>>>
>>>>
>>>>For me to trust caching, it should be application independent. If it works for Word, but not for VFP they (MS, disk manufacturers, or whoever is... caching in) should say so.
>>>
>>>A Frisbee network would work for Word - it has to access shared files only once in a while, if ever. And it always takes the whole file and locks it. Which is why I always had this insane desire to tell the network guy to save that file where the eclipse is permanent. Now if Word could have ten guys pounding at the same text at the same time, and everyone sees what others are doing to the text, and the word count is correct at all times - then OK, forget what I said.