>David -
>
>> 2) on a distribution copy of your classlibs and forms REPLACE METHODS WITH "" this will remove the voluminous copy of the source code from the exe.
>
>Do you mean that we can do this after recompiling all classlibs and before building an exe? Or by "distribution copy" to you mean classlibs that are excluded from the project?
>
>If the former, this would be a great use for the new project hooks in VFP 6.0! Thanks.

If a simple PACK doesn't reduce the size enough you can go through the effort of removing the code.

I say distribution copy because once you've done the replace if you open that classlib you will not have any methods to edit, and I suspect making a change to even a property will cause the class to save without any code effectively "blowing it away". This is clearly a bad thing. The VCX/VCT can be excluded or included that doesn't make much difference. If you have a large classlib that is shared among several apps you can exclude it, then distribute it along with the exes and they can all share the one copy instead of each having their own copy bundled inside. If you have VFP3 you can use the BUILDAPP program it has all the source so you can see what it does to remove the source.