>All of a sudden when I try to compile some apps, I get an error message at the end of the compilation that says "file is not open".
>I have not done any major changes. In fact I tried compiling an app that I had done NO changes, and I get the same error message.
>After that I cannot run the exe at all.
>
>I am really perplexed, and I have no idea how to proceed in determining the problem.
>
>I certainly could use the help.
>
>Thanks,
>Rich Murillo

Have you checked if the anivirus may be involved? If possible try temporarily disabling the antivirus (i.e. use the "suspend" feature if available, or in some antivirus there is a "game mode" which does a similar thing) and try compiling it again. Whenever I saw this sort of problem, it tended to occur on network share more often than it did if it was on a local drive. One of the symptoms would be that instead of the EXE, there might be a temporary file or an intermediate APP. My guess is that VFP is generating the output file in stages -- initially building an intermediate APP file, then processing that file to join with the bootstrapping EXE (using a temporary filename as destination, then renaming it to the final EXE) -- and the antivirus was kicking in somewhere in between the process (e.g. VFP would finish creating some intermediate file, the antivirus would kick in to scan that file -- thus interfering with VFP in opening that intermediate file or renaming it).

On my Win7 box, I would frequently get problem where it would appear that the network share would seemingly go offline intermittently. Finally found out that if I'd disabled the SystemWatcher component of Kaspersky resolved the problem. I suspect that that component would periodically do something on the network and probably interfere with VFP long enough for VFP to think that the network share had gone offline.

Another situation I'd run across is when I was compiling DLLs on a Win7 and Win8 computer. VFP6 would simply hang at the last stage (and no DLL would be generated), and VFP9 would take a while before it spat out an error, and as a result the DLL would not be usable (and TLB and VBR would either be missing or corrupt). Starting VFP as administrator (i.e. right-click on icon, select "Run as Administrator") would solve the problem.