>>Then execute the MAIN.EXE into a separated process:
>>
>>RUN /N MAIN.EXE
>>
>
>Ok, this works. But, while thinking more about it, in most cases, I also got that even if I was not running any app. Just starting VFP, editing some programs and compiling was causing that reaction on the 2nd compile.
I think somebody already suggested the possibility of a file being open? Does CLEAR ALL / CLOSE ALL help? Do you get any messages in the Status Bar? You may have to watch closely for the latter; it seems to me that some messages appear only briefly, and then disappear.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
