>we have a 10 station Visual FoxPro application running on Windows Server 2016 (upgraded from Windows Vista).
>We have 100's of these networks currently running on Windows 7, Windows 8, Windows Server 2003, Windows Server 2016, an so on without any issues.
>
>However, The Local IT Tech stated the following in his most recent email trying to trouble shoot random "Error Reading File" across the network.
>The question is, Is the following statement true?? After I wrote to him that we are using VFP Databases he wrote back?
>
>I was afraid of that. As I'm sure you know, Visual FoxPro reached end of life status several years ago, and file sharing in the newest version of Windows rely on SMB2 and SMB3 for a number of features. I located a number or forums where users of programs built using foxpro are experiencing eerily similar issues, that is, file cannot be read, etc. I am going to trial some setting and rgistry changes on the two design computers, and if successful, will deploy to other workstations. Jen, if you could continue to have staff log errors, and email me them at lunchtime and at the end of the day, that will be a big help. Thanks!
>
>
>
>Thank you.
>Cyrus

Yes, the statement is true, and giving that a part of Windows platform optimization relies on SMB protocol (optimized for web-services and the like, not for file-sharing), I think the best and safest approach is to migrate the data layer to a RDBMS like Oracle, MySql, MariaDB or another one.

Following the Windows evolution says that SMB will keep evolving for optimizing new types of services and applications, and file sharing is not one of them, so client-server is the way to go.

At least, that's my thinking.-