>>We have an app that is composed of one monothilic EXE (approx 10MB). We are interested in breaking it into smaller parts; not because we think it will run faster or use less memory. It's because our users download updates from our website and we're trying to make that faster and easier. Even when compressed the update file is still 1.5 MB. In previous versions, for example, foxbase+, you could create separate FOX files and simply set procedure to. Is there anything approaching this in VFP?
>>
>>One other question, is there any functions available that can determine all available drives on a computer?
>>
>>Any help appreciated. Regards, John
>
>John- You can break up the exe into separate ones like Josh suggested (if your app is logically divisible into separate apps). You can also exclude files form the project like you did in Foxbase. A form that lives as an scx file will work fine when called from an exe.
>
>A couple of other bugs to put in your ear- right click on your project in the project manager and select Project Info. If you uncheck Debug info, this will cut the physical size of your exe by 30%-50%. Be aware that doing this makes all internal information about the program unavailable to an error handler or debuggin utility you might have written. Things like AERROR and LINENO() return no information.
>
>Still another option is a product called RTPatch. Using RTPach, you can take two versions of the same program and create a patch file that contains only the differences. The users can then download the patch, run it, and the their exe will be updated. I don't know the website offhand, but you can download a sample copy. Do a search on rtpach.

Erik - The problem with RTPatch is that if you update frequently, and we do, then you have to have separate patch files depending on what version they are up to. For example, if you have version 1.0 and 1.5 released, then you have to have separate patch files to take them from 1.0 to 2.0, and 1.5 to 2.0. Not practical in our particular situation, but thanks for the thought.

Dropping the debugging info is probably not feasible either because this is an initial VFP release and we are still shaking out the bugs!

Best regards, John