I don't think your situation is about 32-bit compatibility mode. I use 64 bit W7 and don't do any tweak for it. W7 chooses compatibilty mode automatically.

>You may be on to something. I believe the VFP app has to be executed in 32-bit compatibility mode (I am not sure about that though). But I don't know how to enable the app to run in 32-bit compatibility mode.
>
>>I remembered there was a file property at Novell, you can identify files as just run, I remember I had tried this property and it was caused this situation. I don't know maybe there is a feature like that at W7 too...
>>
>>>Thank you for your suggestions, Metin.
>>>I can't understand how the .exe cannot read itself. And the virus infection is unlikely. You see, there are at least 4 different .EXE files residing on the server and every one of them, gives this message. Plus when they start the app from some XP computer, everything works. So the .EXE is fine. Just something in this Windows 7 environment that causes the problem.
>>>
>>>>Hi Dmirtry,
>>>>Two probability on my mind:
>>>>-Your .exe file cannot read itself so can't run.
>>>>-A virus infected your .exe file and it cannot find compiled code from .exe.
>>>>
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>A customer is trying my app on a new Window 7 PC (many other customers use it on Windows 7). He gets, as soon running the application .exe, the dialog window prompting for a .FXP file. Do ... .FXP
>>>>>
>>>>>We even tried to run a very small simple EXE that does nothing with data and we get the same dialog window. Any .EXE we run this prompt for .FXP comes up. Even if I try to run the .EXE as Administrator, the same problem.
>>>>>
>>>>>Could this be caused by some User Account limit to the folder on the server? Any other suggestions?