>>We have an application written in VFP 6 using a MS SQL Server 2000 database that has been in used for several years with all users in the same building. The executable is run from the server.
>>
>>Recently the client opened an office 250 miles away connected by a 6 MB T1 line and has reported that occasionally, users will find data they entered has not been saved. At times they will get the error message "Table buffer for alias "vmit"_contains uncommitted changes".
>>
>>They also report that if two users try to start the program at the same time it locks up with a series of errors Program errors: "invalid seek offset", "error reading file", "file is in use by another user."
>>
>>We suspect that these errors are somehow caused by the 250 miles between the workstations and server, but have not been able to isolate the problem.
>>
>>Any suggestions as to what we could do would be greatly appreciated.
>
>Create a "loader" program that checks the date of the exe on the sever against one that is loaded on the workstation. When a newer one appears on the server, copy it to the workstation and keep on trucking. Make sure all the workfiles, tempfiles, etc are on the workstation too. Another thought, or method, is to use terminal services.

As long as your application is handling/reporting ODBC errors then it would appear that the problem is not with your communications with SQL Server judging from your error messages.

I concur - make sure tmpfiles, workfiles, and all other temporary files and tables are set to local drives - that is what the error messages seem to be pointing to.

Are you using remote views or SPT when dealing with SQL Server? I find SPT is far more resilient and easier to troubleshoot.