>Hi Kevin:
>
>If your tables are on a network, then your problem is the same as thousands of people, so you probably have found a ton of messages on the web and on forums about table corruption, specially memo fields.
>
>Reason is this:
>http://www.dataaccess.com/whitepapers/opportunlockingreadcaching.html
>
>The best solution is to upsize the DBFs to a SQL Database (SQLServer, MariaDB, MySQL, etc), because they have not this problem.

Interesting article, but in case SMB2.x or 3.x is being used, it recommends completely disabling those protocols. Server admins will be very reluctant to do so, given that some features depend on those newer protocols: http://blogs.technet.com/b/josebda/archive/2013/10/02/windows-server-2012-r2-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-smb-3-0-or-smb-3-02-you-are-using.aspx (section 5)

Alaska Software claims to know the details of the problem and offers a patch that changes some SMB2/3 parameters without disabling the protocols entirely: http://www.alaska-software.com/fixes/smb2/overview.shtm

In a perfect world yes, we would all be running against an RDBMS backend. However, if VFP tables are still being used I believe the Alaska Software patch is a good place to start.