Hi Dragan,

I knew about the VCX bloat issue. I'm not experiencing "mysterious growth." Here's what's up with me. I'm leading a team of developers who support 40+ VFP apps which are kept current at 1,000's of sites via modem. To keep the binary sizes small, they've been releasing their procedure library as an APP file.

The problem with that approach is that the system integration group signs off that foo.exe (which calls procedures from the procedure.app) is bug free. Next week, the developers release a new procedure.app which blows foo.exe up.

So, I've convinced the developers that we are going to include our procedure libraries in our exes. They recoiled in horror because of the exe bloat they'll incur. I was thinking that only the p-code Fox needed would be included, but it looks like I was wrong. (Now I've gotta figure out which language it is that I'm thinking about that does that.!)

Thanks Dragan and Steve,

Marty