I believe I have also seen something similar to this when there was no PRG set as "main." VFP sort of decides for itself what should be main and then runs garbage producing all kinds of odd errors.



>This could happen if you try to sign an EXE for an older version of VFP (IIRC prior to VFP8).
>Had also seen this situation when program was processed through program to compress or compact the EXE (you could check to see reported size of EXE file against your original -- make sure they're the same size).
>There was a problem with the file transfer (e.g. transferred via FTP as text rather than binary).-- though this would typically result in a very different error as it'll corrupt EXE badly enough that it probably won't even load.
>
>>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?