>>How do you start another EXE? What line of code your main EXE hangs up on?
>
>Ah, so that's what it means. It's stopped on some line of code and so the "Not Responding" issue? I didn't have a chance to run it interactively last night. I'll do that now and try to see what's going on.

Could be anything - any process which grinds its data without visiting the event loop every now and then is suspect of being stuck. Sometimes it's just a PACK command on a gigabyte table with two deleted records. Takes a long time, doesn't respond to system messages, therefore clinically dead. Which may not be true at all, but Windowses (i.e. all the versions I used) would show this process as "not responding".