No, that doesn't work either, but I believe I figured out what the problem is and it was much more simple than I may have thought...now I just need to figure out how to fix it...

I have an .EXE that calls the .APP. The .APP calls a method in an application object which then calls the do form. The problem is the application object resides as part of the .EXE's project and is instantiated from the .EXE. So when the .APP calls the method then the method is actually running in the .EXE not the .APP even though it is called from .APP. Since the forms are not included in the .EXE project that is what causes the file does not exist error.

Now I just need to figure out how to fix it. I'd rather not duplicate the code for my custom method that starts the form in the .APP project, but it is looking like that is what will be necessary.

Thanks again,
Don

>>Fred,
>>
>>The forms are in the project. I looked at the project info. to see the list of files and visually verified that my forms where checked for being included before I compiled my .APP file.
>>
>>That is the whole problem right there. What I can't figure out is why I get a file doesn't exist error in my compiled .APP file when they were included in the project to begin with?
>>
>>This thing is driving me crazy...
>
>What happens if you specify the relative path in your DO FORM statement? Say you have your project built as:
>

>MainFolder
>    \Forms
>    \Menus
>    etc.
>

>
>so in your code that actually starts the form, you have DO FORM Forms\form1 ? Does that work?