Hi there this is one of them

http://support.microsoft.com/default.aspx?scid=kb;en-us;296264

let me get the others soon
thx


>Hi Joe,
>
>Can you advise the articles that have the OPLOCKS fixes?
>
>Thanks
>
>>Hey thanks again! Checked into this...
>>
>>The power scheme is set to always on which means that the server never goes to standby; so NIC can't go to sleep mode. Drive Write caching is already adjusted as you mentioned it should be.
>>Both OPLOCKS settings in the registry were incorrect, and got changed. We are going to try the app again on the new server sometime in the near future, hopefully this will do it.
>>THANKS AGAIN!
>>Seth
>>
>>>That's good to hear... sort of.
>>>
>>>It does beg the question of how/why the index got corrupted. Do you get that frequently? If not, then I'd say there's still something suspicious going on. Your additional changes regarding OPLOCKS may well fix it, but given the new OS (and hardware?) the settings for hard drive write caching should still be adjusted. And the network adapter possibly going into 'sleep' mode, particularly on workstations, deserves checkout too.
>>>
>>>cheers
>>>
>>>>>Quite possibly a file or index corruption that database validation didn't catch and/or a FOXUSER corruption (if SET RESOURCE is ON).
>>>>>
>>>>>VFP8 and 9 support a SET TABLEVALIDATE setting that can catch (and help resolve) a lot of these issues.
>>>>
>>>>Thanks everyone. One of our tables/index was corrupt, but validate does not catch it. Do you all recommend we certainly update from Fox7 to Fox8 or 9?
>>>>
>>>>We discovered that Win2003 server actually has TWO registry settings to denote if Op-Lock setting is enabled or disabled. Also, my server coworkers just told me Op-Lock was ENABLED. Do you think this lead to the corruption?
>>>>
>>>>We definately need to DISABLE Op-Lock... correct? This has fixed issues for us on WINNT and WIN2000 server.
>>>>
>>>>THANKS ALL