>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

If you also get 'cannot lock file', try this.

To resolve this issue, increase the value of the IRPStackSize registry entry.

To do this, follow these steps:
Click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
If the IRPStackSize entry is not present in this subkey, follow these steps:
Click Edit, point to New, and then click DWORD Value.
Type IRPStackSize, and then press ENTER.

Note Type IRPStackSize exactly as it appears. The value name is case sensitive.
Click IRPStackSize, click Edit, and then click Modify.
In the Data Value box, type a larger value, and then click OK.

Note Values may range from 0x1 to 0xC. These values are equivalent to 1 to 12 in decimal notation.
If the problem persists after you complete the previous procedure, increase the value of IRPStackSize more.

We found setting this to 60 did the trick.