Hi Jim,
Just following up on previous thread. Have a look at this thread on Wiki http://fox.wikis.com/wc.dll?Wiki~PersistentIndexCorruption

Regards

>Thanks for the link to the links, Neil.
>
>I've read a few places that recommend turning off "opportunistic locking" and fewer places that actually tell you how to do it.
>But, so far, NONE say what estimated impact it will have. Seems we don't need to know. Sadly, I feel I need to know.
>
>There are also (possibly, could be the result of loose writing by MS) contradictions between what I read in such articles (including the one referenced) and the operation of the Redirector as described by MS.
>In the writeup I used MS was quite specific that any write (including update) done on a client to a non-resident data store is immediately intercepted by the redirector and forwarded to the storing (controlling) system.
>***IF*** this were the case, though, then it would be hard to understand how we could be seeing what we are (increasingly) seeing.
>
>All in all this stuff seems to be held close to the vest by MS, apparently relating more plausible than actual details in writeups.
>
>It really would be interesting to hear from folks who use non-Windows OSes or server hardware.
>
>cheers
>
>>Hi Jim,
>> Have a look at the link to Dataaccess in Thread ID: 834142 Message ID 834155 it sums everything well. The only other thing to look at is Disabling Write Caching, i.e. user exits app locks not clearing till cache refreshed. i.e. 1-2 minutes