I've seen this too, using VFP 8.0, also on XP although I'm not sure that matters. Rightly or wrongly, I always attributed it to my code leaving things hanging - dangling object references, unreleased memvars, etc. - after running the app from within the IDE during development, when clean-up isn't as complete as it should be for a production app. I find if I run my 'reset environment' macro each time after I run an app during development, I don't get the freeze ups on subsequent builds. It's unscientific, but seems to work.

FWIW my reset macro is as follows. The only reason for turning off editor options is to disable intellisense while all those commands are running in the command window.

_VFP.EditorOptions = ""
on error
on shutdown
cancel
clear all
close all
clear program
release all
set talk off
set deleted on
clear
set classlib to
set library to
set status bar on
set notify cursor on
set message to
_VFP.EditorOptions = "LQKT"

>I had this situation after a while with VFP 8 and now still have it with VFP 9. Basically, I have an application that works fine. I can start VFP, modify my project, build it and run it. It finishes ok. Now, I am back into the modify project and try to build it a second time. VFP will simply freeze. I think this is also related to the same problem that my application, when being run from the desktop, from Main.EXE, will not terminate once I finish. The application will remain in the task bar for about two minutes until it goes away by itself. I only have this since I have upgraded to XP. I never found the problem. However, now I have this VFP project that I need to work on and just can't afford to close VFP everytime I run the app before building it again. We talked about that a few months ago. I never found the problem but now I need to resolve that issue once and for all.