Thanks for the background.

Agreed, if you need high performance, data access over the wire is a limitation. Gigabit Ethernet has a maximum theoretical throughput of about 120MB/s, in practice it's usually quite a bit less. A single modern magnetic HD can pump sequential data faster than that. A single consumer SATA SSD can push over 500MB/s both read and write, and NVMe or PCIe can be even faster. Mainstream network speeds haven't kept up with recent advances in SSD performance, so for now, if you need fast storage, local is the way to go.

>I did not update the registry as described by Alaska Software I just moved the database back to the local server. The other reason I moved the tables back was due to customer complaints about the reduced application speed when the tables were located on a Server2. I had dual network cards in the server. One network card was dedicated to accessing data on Server2 and the other network card was for the RDP connection. I wanted to see if a dedicated network card would improve the speed of data access across the network in fact I was hoping to test some high end network cards that support RDMA on 10 gig Ethernet but had to settle for good quality 1gig cards. The performance was usable but not great. On our newer installations I have chosen to use SSD drives in the servers and the performance is great and the users are happy and I do not have index corruption etc.
>
>>Hmm, interesting. When you were seeing the index corruption when your data files were on a different server (call it "Server2"), do you remember if you tried applying the Alaska Software recommended registry updates to your Server 2012/2016 RDS server (call it "Server1")?
>>
>>>I run my applications on Windows Server 2012 and 2016 using Remote Desktop Connections but I keep the data local to the server and all the application run fine in this configuration. I have tried putting the data on a separate server but I found I got index corruption so I went back to host the data and applications on the same server.
>>>
>>>Simon
>>>
>>>>I read over here that there could be problems running VFP apps on windows server 2012 or windows server 2008. Is it the same with Windows server 2016?
>>>>
>>>>I didn't read a lot so I'm not sure what the deal is in those cases where there's an SMB problem. Could you please tell me what would be a cure for that problem and give me informations so I can really understand why this is happening?
>>>>
>>>>TIA