Sandi,

I think you found the problem. I was migrating a project from Windows to
MAC and I had not transported all my Screens and Report forms. I tried two
things. I reinstalled Foxpro for the MAC and then I transported each and every
Screen and report form. After this I was able to compile. I just wish
Foxpro had given me an error message that it could not complete the
executable. THANKS AGAIN!

>I'm not sure if your problem is restricted to MAC stuff but I have a
>Fox2.6 non-MAC app and this happens when the project cannot find
>something for a screen. It gets to a certain point and dies and usually
>the culprit is found to have no screens set up in the Edit screen set
>dialog box. What happens is it stops the whole process without an error.
>To find the culprit I usually check things I've just changed.
>
>Hope this helps.
>
>Sandi Cassidy.
>
>
>>
>> > I am suddenly having a problem building an .APP or .EXE file on the
>> > Macintosh side. It was working and I cannot for the life of me
>> figure
>> > out
>> > what I changed. When I use the project manager or BUILD EXE
>> command,
>> > the
>> > system merrily chugs along looking for all the world like it is
>> busily
>> > building an APP or EXE file. It DOES NOT give me an error message.
>> > When
>> > it is finished there is no APP or EXE file in sight? Anyone else
>> > experience such a problem?
>>
>> Is there another .EXE somewhere else in the FoxPro PATH? If so, you
>> might be replacing it, instead of creating one in the current
>> directory. And if it's marked as ReadOnly, or if other users are
>> using
>> it at the time that you're trying to erase it, then you won't be able
>> to
>> delete it and you won't always get an error.
>>
>> This one's only bitten me a few times, and it was a royal pain to
>> find.
>>
>> /Paul