>>Hi,
>>
>>Again, a customer is having a problem running VFP 9 application. When they start the application .EXE file they get the window DO and the File of type shows "Program (*fxp)". I have tried several different .EXE programs (different programs but all built with VFP 9). The customer also tried to reinstall Windows 7 completely. The strange thing is when they reboot the computer the program(s) work one time (no problem). When they close a program and start again, the problem with DO *.FXP appears again until they reboot the computer.
>>
>>Any suggestions to where to look? TIA
>
>With VFP6 programs I usually kludged things on those occasions by:
>1. Copy the EXE to one with APP extension
>2. On affected computer, install the VFP6RUN.EXE program on local "Program Files" or "Program files (x86)" folder
>3. Change shortcut on those affected computers to launch VFP6RUN.EXE and add the APP file as command line option, and set the initial directory to the directory in which APP resides.
>
>Okay, so it's not really much of a solution, bur rather a workaround.
>
>One thing that we might want to check is to see what permissions we've got on the folder in which program resides. IIRC when we compile a program to EXE in VFP, it isn't a standard PE file, but more like something like the runtime launcher "stub" that has the APP file appended to it. If for some reason the EXE isn't able to open itself as a datafile, you get this sort of problem. IIRC this sort of problem used to happen on Novell network where you set the EXE with the "copy inhibit" attribute.
>
>On other occasions, this sort of problem seems to occur when the program is built with a different version or revision (or patched copy using ReFox or equivalent) than what is installed (or is in memory at the time) of the runtime -- essentially a "DLL Hell" scenario.

Thank you for your input. I will see what apply in the case of my problem.