Mike,
A variation of it was already done (see "if .F. ... endif" at bottom).
Cetin

>Drew Speedie showed one way to deal with this problem is to have a never-to-be-called procedure in the main prg file.
>
>PROCEDURE PMFAKEOUT
> EXTERNAL FORM form1
> EXTERNAL FORM form2
>ENDPROC
>
>In MaxFrame a project hook updates this procedure as new files are added to the project. When you rebuild your project, everything listed there gets pulled in.
>
>This has been in place since VFP5 at least. It doesnt' just apply to execscript, but also to macro-substituted references.
>
>>>Old version of the application was build under VFP7.
>>>New version was developed using the old projectunder VFP9. Forms are not called directly like:
>>>do form formname
>>>
>>>but formnames are in a table included in the project - table has field action:
>>>DoForm("formname",'parms')
>>>FormMethod('methodname','parms')
>>>etc.
>>>An 'executor' object handles what to call based on that data. This worked very well in previous version.
>>>
>>>New forms/classes/frx/prg/prg based classes etc were added in new project (files needed are explicitly added -included- to the project). After build however the exe complains about missing files. ie:
>>>
>>>c:\exepath\formX.scx doesn't exist.
>>>
>>>but that form is explicitly included in project. Did anybody encounter this and know of a quick solution? (I'm going to add
>>>if .f.
>>>do form ...
>>>do this
>>>do that
>>>endif) but I don't think it'd do.
>>>TIA
>>>Cetin
>>
>>Solved somewhat (still parts to check). Cause was ExecScript(). If form is called via execscript then it fails (a bug or a by design???) and doesn't see files included in project.
>>Cetin