>>
>>John
>
>John, there is also this from Microsoft which offers a "fix" ... https://support.microsoft.com/en-us/kb/2028965/en-us
>

Out of curiosity;
Did anybody tried this official solution ? What is the outcome/verdict ?

I was very pi$$ed back then when I learn about existence of the problem, especially in combination with demise of VFP as tool...
However my personal experience so far is that (for me at least) this is NO ISSUE not so ever!
I am using buffering and transactions throughout without exception (framework design) and so far (knock on wood) no issues!
No registry hacks not so ever and yes with SMB2 and later enabled. Of course this is anecdotal evidence but it is what it is.

To John;
My take is that if application was properly done at first place, SMB2 bug might not necessarily affect it. (but cannot be 100% guaranteed though)
Just like 'back in those days' ;-) when properly written apps could survive even in bad network/power supply conditions, whereas badly written apps could corrupt data even in perfect network/power supply conditions.
(and some conveniently blaming those problems on VFP shortfalls {g} )

Good thing about this is that _there is_ 'official' solution from M$ on this one.
It can be useful 'argument' in usually useless discussions on VFP longevity and such... ;-)