Which is way I said "suggest": I agree, it hasn't been proven.

>Thanks - but the way I read that thread, the OP was investigating a speed issue with a VFP app, not corruption per se. I don't see any explicit testing of Brandon Harker's repro code under various OS/connection combinations.
>
>Also, there's no mention of any antivirus products or disabling of same. My understanding is some AV products have caused those exact symptoms with multiuser VFP apps.
>
>So, because:
>
>- Brandon's code was not tested
>- Antivirus was neither acknowledged nor factored out of the testing that was done
>- According to the OP, all workstations were Win7, so they were not even using SMB3. SMB3 is used only with connections amongst Windows 8 and Server 2012 hosts
>
>I don't think that thread proves SMB3 fixes the problem introduced with SMB2.
>
>>Hi Al,
>>
>>here is one: http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/8d8a00c1-b497-4fec-b894-40ff73e7fe42/ (down the thread, to a post on Wednesday, November 28, 2012 1:18 PM). I could have sworn the other post was on the UT, and even renewed my subscription (Michel, you should thank Al for prodding me into it <s>) to search, but couldn't find it. I had seen at least 2 mentions before that, but have no luck finding them again.
>>
>>Hank
>>
>>>Got a link? I saw your similar post on the Lianja forum but no further details there.
>>>
>>>>There was at least one report, on the UT I think, of Win12/SMB3 solving the problem.
>>>>
>>>>Hank
>>>>
>>>>>>We currently run our VFP 9 and Foxpro 2.5 applications on Windows 7 32 bit workstations. The server where the tables reside is getting past EOL, and our network guys want to move the tables to a 64 bit virtual server.
>>>>>>
>>>>>>Does anyone anticipate any problems we may be facing? Of course we will test this configuration before placing it into production. Everything I've been able to find online has to do with VFP on a Win7 64 bit client, or SQL Server 64 bit trying to access VFP tables. Neither of these scenarios is what we are going to try and do.
>>>>>
>>>>>One problem with newer servers is not that they're typically 64-bit, but that by default they use newer versions of the SMB file-sharing protocol.
>>>>>
>>>>>SMB version 2.x used in Server 2008 and later can cause corruption with VFP/FoxPro, MS Access and other flat-file databases:
>>>>>
>>>>>http://support.microsoft.com/kb/2028965
>>>>>http://support.microsoft.com/kb/2618096
>>>>>http://www.caseware.com/support/caseknowledge/kb-271
>>>>>
>>>>>MS has issued some hotfixes but my understanding is these do not fully address the issue(s). There is more information in Thread#1511813 . Brandon Harker has kindly been "taking point" on this issue with MS. He has developed some repro code in Message#1461761 .
>>>>>
>>>>>SMB2 can be disabled which is a workaround for this issue. However, network or sysadmins will be loath to do this on servers. Disabling it on workstations will force the server(s) to fall back to SMB1 when talking to those workstations, without having to reconfigure server(s).
>>>>>
>>>>>With Windows 8 and Server 2012 MS has introduced SMB 3.0. I have not heard of any test results using that combination, or with earlier OSs.