>>I have a customer where the cdx file continues to be corrupted.... I rebuild indexes (i use for this operation an old version of Stonefield Database Toolkit) and after a few time (even 3 times in same morning) i have to rebuild it..... Table's size is 450Mb and in the cdx files i have 35 tags. We works in rdp session on a server with Windows Server 2012 R2 and 32Gb ram. (this is a phisical machine). The users are using my app are from 6 to 10 and this is the table that probably is used by all the users (both for write and read access)......... Someone has had similar problems ? Some suggests.... This customer uses my app since 2005 and we never have had this problem and the table thta now has problems was in some periods larger (near foxpro limits) and we have moved data to another table....
>
>I almost suggested to check for SMB2 bug (upgraded to SMB3), because it's probably irrelevant whether two processes access the filesystem through network shares or by running in parallel on the same machine - it's the same filesystem. But then this bug is around for a dozen years (since the Vista? that's 2007...), so why would you have the problem now and not last year?
>
>Soooo... I'm just mentioning this as something to check, but I don't think that's the cause. I'd rather check what was installed on the server around the time this started happening - what updates, which services are now running that weren't before, that kind of thing.

SMB2/3 might still come into play if the remote desktop host isn't the same physical computer as the one providing the file storage. We had run into situation where customer was complaining that our application ran *significantly* slower on the newer, much-faster server that replaced the old one. They claimed the new server was configured *exactly* like the old one. Upon closer examination (though a remote connection) I'd noticed that the application resided on a network share -- I'd enquired if this was the same as the original server. At first the response was "yes, it's exactly the same", though with a bit of discussion on the other end, they responded "does it matter?"
I responded "it might -- where was the application on the old server?"
Their response was "on a local drive."
I'd asked "a drive local to the rdp server?"
"Yes"
"That could make a difference. Where is this network share (that the new server is using) reside?"
"It's an off-site network server"