>>I looked a couple of .PRGs created by Rick Strahl (I am using one of his tools in my VFP 9 project). And he put many functions, procedures, and classes in just a couple of .PRG files.

Just when the furor was dying down.... ;-)

But "Encapsulation" would be a good reason for 3rd party commercial offerings to group functions into a proc rather than bulking out the project manager with huge lists of internal functions to distract the developer.

BTW, if it's accepted that a prg/fxp in your project *is* loaded into memory at startup with the rest of the app, then an fxp "file read error" suggests either something (virus scanner?) is able to lock memory supposed to belong to your app, or the app is trying to access a copy other than its own. The developer's %temp% path could be a clue; definitely check the path to the prg in project manager since file read error could simply signal an attempt to access a %temp% other than the user's.