Need help with strange problem VFP 9 SP2

Question

I have an  exe running on 11 workstations in a domain server W2003 environment. This app has worked flawlessly since October 2007. I have one workstation that is all of a sudden having problems staying connected with the server.  The hardware people are trying to address that.

An unusual result of this connectivity issue is that the workstation will throw up an error saying it is unable to Read File F:\myfolder_x\myproc.fxp

What is strange is the "_x" at the end of the folder name it's displaying.  The server does not have such a folder, the program resides in \myfolder.  The procedure file that it's now unable to find was created in \myfolder_x and then renamed to \myfolder.   

A text search reveals that the fxp does contain the folder name \myfolder_x. Is this because this is where it was last compiled?

Any idea why the workstation would be trying to read the file from \myfolder_x when that folder does not exist?

I have checked and there is no hard-coded reference to a folder name anywhere in the application.

Thoughts?

Thanks!

---

Dick Day

Answer 1

When you build an executable, the exe remembers where the fxp file was sourced from if it is not in the same place as the project file. It will save the relative path if the fxp is in a subfolder of the folder where the project is. otherwise it will save the full path. That information does not normally matter when running the application if the FXP is embedded in the executable. 

Answer 2

Thanks. The file in question is excluded from the exe, as are most of the files.

So, do you think it's possible that when the workstation loses connection with the server, the program, still residing in memory, is looking for this file in the original project location?

---

Dick Day

Answer 3

Look at the Temporary Directory on the "wrong" workstation...