>If "topic" revolves around SMB2/oplocking problems of remote .dbf/.fpt/.cdx files corrupted due to MS crippling the protocol for ISAM usage, I can only advise NOT to try to steer upriver without a paddle. Before SMB2 you had to weigh ease of install vs potential speed problems.
>
>Under SMB2 or SMB3 there are several ways to increase protection from data loss, but IMO you cannot compete on economic reasons with SQL backends already having implemented all those protections (and more...) years ago and eliminated all bugs encountered since then - esp. as some of those are free or without cost at smaller usage.
>
>I dislike MS removing the choice for us as well, but dislike burning money or programmer time more ;-)
>
>If you think about other reasons, pls. be specific.
>
>my 0.02€
>Thomas

Thanks Thomas.


>
>>I suspect this topic has been dealt with before. Can someone give me some links and general advice on when Microsoft Windows changed a setting which has the potential to cause data loss and how to correct this before it happens using latest release of VFP 9. I believe it is a regedit setting.
>>
>>I am hoping there is an install package I can include that will take care of this.
>>
>>Thanks in advance....