>I do not understand. I want to be able to test and make changes in my excluded prg through out the day, without having to touch the exe each time.
>
>I do compile the prg each time and then copy the .prg and .fxp to the property folder for the exe. But what is a CLEAR PROGRAM?
>
>
>>>I have a prg that is excluded from the exe. While I am testing, I am copying over a new .prg file, but when the exe tries to execute the .prg code, it seems to keep the older .prg copy. How can I force the exe to get the new .prg each time, without having to get out of my application?
>>
>>Two things to try: compile it, and Clear Program. Maybe both.

I meant from inside the exe. Maybe you should

compile (yourprg)

during the startup of the exe.

As for Clear Program, that should clear any cached fxps in your exe. Here's what help says about this command:

PROGRAM
Clears the compiled program buffer. Visual FoxPro keeps a buffer of the most recently executed programs. In rare cases, Visual FoxPro might not recognize changes made to program files on disk. CLEAR PROGRAM forces Visual FoxPro to read the programs from disk, rather than from the program buffer. The most common reason Visual FoxPro might not recognize changes made to program files is your using an external or terminate-and-stay-resident (TSR) editor to modify a program file. With this exception, you should not have to use CLEAR PROGRAM.

The TSR remark used to apply to SideKick-style editors back in the days of FoxPlus... and the whole text generally applies to the IDE, but it should work the same in runtime.