If I don't delete the PRG, VFP will actually add the PRG file instead of the FXP file. Also, I can't drag & drop the FXP files from Windows Explorer into the project.

I can however, add the FXP file by explicitly selecting it when prompted by clicking the ADD button of the project. This will be a very tedious task if I have to do this for all compiled files.

I am trying to send a distribution project to our client containing the application codes (PRGs) with our framework compiled FXPs and objects.

>Don't delete the prg. Not exactly sure why it requires the .prg to be around, but it appears that that's how it works.
>
>
>>Hi all,
>>
>>How do I add an FXP file to a project programmatically? Consider the following snippet which I thought would have added the FXP file.
>>
>>

>>* create a test program
>>strtofile([wait window 'Hello World'],'test.prg',.t.)
>>* compile the test program
>>compile test.prg
>>* delete the test program
>>delete file test.prg
>>* create a test project
>>modify project test nowait
>>* add the compiled file
>>_vfp.ActiveProject.Files.Add('test.fxp') && does not add the file!!!
>>

>>
>>TIA.