>>We have an older VFP application and need to keep it running while a newer version using SQL Server is completed.
>>
>>Our client needs to replace the existing file server, and we are well aware of the SMB problems with newer Windows servers and shared DBF files.
>>Clients are expected to be a mix of Win7 and Win10
>>
>>What is the recommended fix now?
>>
>>Give up on Windows Server and use linux/samba to host the dbf files?
>>
>>Win2008 with a patch or registry setting?
>>
>>Win2012 or Win2016 somehow?
>
>I've been trying to stay on top of best practices for this. You might want to review
>
>Message#1661729
>Message#1620274
>
>The recommended registry changes are workstation/client-side, they should be applied whether your back end is an actual Windows server, or Samba on Linux.
>
>I have one client running a VFP5 app against a Samba back end. It generally works fine. We had an issue about a month ago where the admin did some tweaking and set Samba's Strict Allocate to Yes - that caused some "File not found" crashes in the app. When set back to the default "No" value, we've had no problems since.
>
>It's worth pointing out that Win7 and Server 2008/2008R2 go end-of-life 2020.01.14 (a little over a year from now). If you want a new Windows server go with the latest version.

Thanks!