>I assume you're worried about the size of your exe, because you may need to distribute it over a slow connection, right?

Yes, this is a concern. Since our programs are located on the network. And user's access them from there. I don't want the user loading a huge app over the WAN. Or even locally. I've noticed the major user complaint is SPEED!

I converted 1 program that was 850K in size to use a new 'test' class group. It became 1350k. This was not due 100% to the class. But the class alone was a bloating factor.

>So, the first thing that crossed my mind is to reduce the memo bloat in classlibs - that was a weak spot in vfp6. Second, you may write an utility which would check your project for unused classlibs. I've seen that a lot; a classlib gets included into a project at some point, and then kept there even when the classes in it are not in use at all. It gets compiled into the exe each time.

As a practice, if the application has undergone a serious overhaul. I tend to remove all the Classes from the project manually then recompile. Only the Classes that are truely part of the program are re-attached. This seams to clear up most of the excess junk.