>I have a large number of FoxPro apps that have been in constant development for 15 years.
>
>When we attempted to move to Windows Server 2008 many years ago, we encountered corrupted DBFs due to SMB1 issues. We reverted to Windows 2003 and have remained there ever since.
>
>We are now considering using Windows Server 2012R2 and have a question of anybody who is using Windows Server 2012R2 without encountering corrupted DBFs:
>
> --- What changes (if any) were made to avoid DBF corruption issues in Windows Server 2012R2 ?
>
>Thanks in advance

We have had this issue in all of our systems. The only true system fix we've found is to disable the impacting cache options. One of the team leads created a script which would set the correct registry values on the client's machine when the setup app was run. It slows down their network access on servers that use the older protocols, and is annoying as all get out when accessing those systems in Windows Explorer, for example, but it does prevent the errors from coming into the data.

It's not an ideal solution, and it's caused many customers to seek to migrate away from file server-based systems to client server systems.

We've also attempted work-arounds to introduce journaling and a way to validate that what we think should've been written was actually written, and what records we think should be index actually are.

If there was a system to repair damaged index files while they are in use, it would be an option as well as you can write local copies of data going to network files, and validate they're there later, and then on next search / sql query, run the quick index validation algorithm for those new records you know should be in there, to correct any integrity issues on the fly. To my knowledge, however, there are no index repair utilities that work on the fly while the indexes are in use.