And - James - here's another suggestion I found out recently when I was looking for an answer to a different VFP problem I was having. I kinda stumbled across this - although, its one you may NOT want to actually do - since it would probably mean you would have to have a COPY of your project - and Generate the EXE with that COPY.
Supposedly, if you Compile your screens, then this Object Code get generated and implemented within the Screen code (in the SCX or SCT file). After compiling - you can actually Remove all your actual Code in ALL your Methods. And, supposedly - that will GREATLY Shrink the size of the EXE. But, it's a tricky way to do it. Again - probably NOT something you want to do - but, I found it interesting when I stumbled upon it... -K- -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Alan Bourke Sent: Monday, March 04, 2013 11:53 AM On Mon, Mar 4, 2013, at 03:17 PM, James Harvey wrote: > I'm trying to remember how to go about making the exe "smaller". > Aside from not including debug info as others have said, don't include anything static either like DLLs, FLLs, report files, graphics - anything that is not vital to the project building successfully is a candidate. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/208B5C6E6E9D4615A6F28A911D3259FD@Programming2 ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
