>Okay, I think I've got my wires crossed. I've been reading a little about C++ lately and I think I've got my compilers mixed up.
>
>If you have a procedure library with 100 procedures in it that you include in your app, I was under the impression that the only binary ("p-code?") that gets put into your exe is the actual procedures that you call.
>
>I tried it out this morning (VFP 6) and was able to consistently prove that to be the case. But, as is usually the case, when I asked my partner to come look at the results it stopped doing it and now the exe increases in size whether the procedure library is referred to or not in the application.
>
>Does any of this ring any bells for anyone?

If you once (during the lifetime of the .pjx) file had a "Set procedure to blabla.prg", the .prg will be included until you manually remove it from the project. The whole file (compiled) will be included.

The growth of the executable may come from other sources, like .vcx's memo bloat. You may try to open each of the .vcx exclusive (I don't remember exactly if there are any other types of files which don't get packed and written afresh when edited) and pack them. Then recompile and see if the executable shrinks.

The reason for the memo bloat in vcxes is that they're opened shared, so more than one person can edit different classes within one. It doesn't lock the whole library when you edit one class, only the records this class consists of. When you save, it writes new blocks of memos for any methods or properties you changed, and of course doesn't remove the old ones. And your exe grows.