Hi Fred,

I tried putting in the "dummy" procedure that you suggested and I put DO FORM's in the procedure as you said, and still get the same results... file does not exist?

Any other ideas?

Thanks,
Don

>>The .APP doesn't function by itself. It only works with the main .EXE file. So I wouldn't want someone to run it from the Windows Explorer or something like that. They way the application works is there is a main .EXE and the their are 3 additional modules which are all .APP files. Some user have one module, some have two, and some have all 3. By putting all the forms for the modules in a .APP, it makes it really easy to distribute the compiled version of the our product. Or at least it used to be easy... :)
>>
>>-Don
>>
>>>just out of curiousity, why would you distribute the App as App file as opposed to exe?
>
>
>Create a piece of code that has your forms in it like this:
>
>

>* dummy.prg
>*
>*
>DO FORM form1
>DO FORM form2
>DO FORM form3
>

>for as many as you need.
>
>Just be sure to manually include this file (dummy.prg) in your main code in some way that it will never execute:
>

>IF .F.
>  DO dummy
>ENDIF
>

>
>Or for that manner, you can add at the end of your main .PRG a dummy procedure that never gets called:
>
>

>*your main.prg
> your code here
>*
>PROCEDURE dummy
>DO FORM form1
>DO FORM form2
>DO FORM form3
>

>
>Any of the above methods will force the Project Manager to add your forms to the .APP when it's built.