>HI Everyone!
>
>I have a problem that I'm dealing with that I'm sure others have wrestled with. Recently we moved our VFP application from a Windows 2003 server to a Windows 2008 R2 server and have started having issues with DBF file operations taking a long time to process. For example in one place it was just doing a SKIP through a DBF with about 20k of records and the coverage profiler was saying it took 3 minutes. But in other places it seems to be working fine. At other times it will open a table Read Only even though it's not coded to. Or we will get file locking errors. At times there can be up to 90 users in the system that are hitting these tables so we think this might be some of this issues, but then in other places no one is in the system and it will take forever to run a process. This is a legacy app that does old time methodology of table locking. No table buffering is being used either.
>
>Has anyone had any experience with Windows 2008 issues? I know there are posts about SMB2 and Optlocks but we don't think that applies here because this application is not run over a network, but rather users remote in via Terminal Services and run it right on that server. MS even says on their website that this SMB2 doesn't apply when running on TS. However we did try disabling these at one point and it brought the system to a crawl. Also the vfp exes are running in Windows 2003 emulation mode and while that seems to have helped a little, we still are having the issues.
>
>So is there anything else anyone knows of to make VFP and 2008 play nicer together? Also, we haven't done any testing on 2012 Server but are wondering if it might be better in this regard.
>
>Any guru help would be greatly appreciated!!!!
>Thanks!

Is there an antivirus installed? I'd seen many situations where it wasn't the server OS but an overzealous antivirus getting in the way.