>>Hi Tracy.
>>I saw this thread as well, but his problems seemed to be repeatable and more specific to Win2000 early versions. Whereas, we are not seeing any patterns related to the operating system. We do have the cache/delays/sleep on network cards turned off as well.
>>I was hoping for a consistent "yes, we all update the registry" or "no, that is not really the issue".
>>Thank you, though, for your response.
>>David
>>
>>>>Issue: Corrupt Memo Files
>>>>
>>>>Hello all.
>>>>
>>>>Memo fields (FPT files) are a great asset to our application. Regardless of our efforts to create "tight code", we continue to experience random corrupt FPT files. The problems are rare, but nonetheless irritating. Sometimes, the corruption is logical and due to HD cacheing, virus scanners, power outages, and questionable networks. However, we've also had memo file corruption in offices where the networks were stable and nothing had changed in years.
>>>>
>>>>We've been using VPF since v2 and are currently on VFP8. The application has been stable in a variety of multi-user environments, in over 1000 offices.
>>>>
>>>>Typical Environments:
>>>>Peer-to-peer XP-Pro SP2, Server2003, Server2000, Win2000. Always Cat5 and 100MB networks. We always have our customers disable Windows automatic updates, virus scanners on our folder, and the cache on all hard drives.
>>>>
>>>>Cacheing the writes seems to be key to many data corruption issues in a multiuser environment. Further investigation has led me to articles detailing the registry settings for EnableOpLocks and EnableOpLocksForceClose in LanmanServer and LanmanWorkstation. (Microsoft article ID 296264 and 126026, and an older article on Superbase.com).
>>>>
>>>>Questions:
>>>>1. Should we set the two registry settings mentioned above on server and client PCs, telling the OS not to cache?
>>>>2. Has anyone found that XP-Pro SP3 is causing more problems with FPT files?
>>>>3. Is it common to also disable Shadow Copy that copies files in background throughout the day?
>>>>
>>>>Thank you for any advice, experience, and/or opinions.
>>>>
>>>>David
>>>
>>>Generally, yes. You'll want to do some testing. See:
>>>
>>>Re: Strange Corruption Thread #1053347 Message #1053841
>>>
>>>However, I recommend Stonefield Database Toolkit (SDT) and FoxFix.
>
>With regards to Windows XP SP3, apparently it resets various OpLock settings to the default: Thread#1325361

Hi Al.
Yes, I saw that. His comments implied that they set up their customers with EnableOpLocks Off, which is not the default for the OS. Coupled with the other articles from Microsoft and Superbase listed above, I began to think that this is common knowledge and everyone sets up the registry to avoid memo field corruption.
It'll be interesting to see what others are doing.
Thank you for your input.
David