>>At least we know that BUILD EXE command isn't responsible for that problem because it's executed in the separate memory space. :)
>
>Well, until bug fixed or cause of the problem known, it's difficult to assume on that.
>
>The reason I'm saying this is because it's on that line that it generates that error.

As it seems the problem could not be solved, maybe you can try a brute-force approach, either by trapping the COM error and retrying, or testing after the build if the EXE has being generated, and if not, running the copilation again.

So at least you don't have to be alert about the failure...

Hope this helps,