>>Assuming you are building from the project manager, have you tried building from the command line instead? If you can successfully rebuild from the command line then the problem is likely in the Project Manager.
>
>As a workaround for that, what I have done is to create the EXE icon on the desktop. Whenever I build, I run the EXE from the icon on the desktop instead. So, the memory does not get all mixed up. I am ok using that approach.
>
>I'll let you know however about the command window. If I recall correctly, this was not changing anything.


Pardom for jumping in. I too have this same problem when I try to build the tool LifeCycle Build Cycle. I was unable to run the application then build the application right afterward. After fooling around (for hours) I finally found a set of command that rid my VFP envirnoment of what ever was causing the freeze up.

Here is the Build.prg I came up solve it.

* Program:     BUILD.PRG
* Description: Build the Exe for LifeCycle Build Cycle application
* Created:     05/07/2004
* Developer:   Gregory L Reichert
* Copyright:   Copyright (c) 2004 GLR Software
*------------------------------------------------------------

IF ATC("MERLIN",SYS(0))>0
*	CD "c:\lifecycle"
ENDIF

ON ERROR
ON SHUTDOWN

CLOSE ALL
CLEAR ALL
=SYS(3056)		&& re-read registry

CLEAR PROGRAM
SET CLASSLIB TO
SET PROCEDURE TO
SET LIBRARY TO

CLOSE DATABASE ALL
CLEAR ALL
RELEASE ALL EXTENDED
CLEAR DLLS
CLEAR MEMORY
CLEAR RESOURCES
=SYS(1104)		&& purge memory buffer
ON ESCAPE

SET RESOURCE ON


*--------------------------------------------
*  Build exe
*--------------------------------------------
BUILD APP LCBuild FROM LCBuild RECOMPILE


RETURN

I did discover that the problem stop when the CLEAR RESOURCES was executed. But also, the other command prior to it must be execute too.

My 2 bits