>I have a vfp program which uses about 30 files - when run it brings up an error index does not match file
>
>When I connect into this machine remotely via Logmein and run the program I do not get the error and the program runs ok
>
>When I run this program on another machine at the same site I do not get the error and the program runs ok
>
>How can I find out which file the system is referring to - I would guess its referring to a file on the c: drive hence it runs on other machines but why is it OK when I run it remotely?
>
>Has anyone heard of a fault like this before?

Some things you could check:
* Time and Date could be out of synch between workstations and servers. This is one thing that is easily resolved but sometimes a real head-scratcher to figure out -- especially if you forget to check *both* the displayed date and time *and* the timezone -- this is important since Universal Time is often the time-base for the filesystem. Depending on how you've got security configured, sometimes having time off by a few minutes is enough to cause connection issues.
* Network issue (runs OK on local system, sometimes have problems across network -- running through remote desktop is same as local on computer hosting the files). Could be the same old issue that started with Vista -- SMB2 (and later) causing issues with shared files. There are various registry patches that can be set as a workaround (though annoyingly these could get reset after a Windows Update). I've also seen a few occasions problem was traced to faulty hardware (bad cabling, switch going bad, network card going bad, etc -- in this case you're probably apt to see problems in other areas involving the network and not just the application).
* Permissions issue -- in usual cases making sure to check both Security and Sharing tabs in the folder property works (as in typical case, files and folders contained within inherit the permissions of the containing folder) -- though I'd run across a few situations where the contents had very different (in this case, forcing the child entries to gets them back in synch). Sometimes this sort of thing could be triggered a user is deleted in Windows and ownership of the files and folders gets messed up (in this case the fix would be to assign ownership by existing user), or when files were restored from a backup (and there was a change in security or sharing information). If using a Unix/Linux host with SAMBA, there are the few occasions I've had to start a console session to the host fix these at the host directly (the access rights were OK at the SAMBA level, but not at the "native" level in Unix/Linux).