I don't know if VFP just sets a handle and waits for a specific request or if it is all loaded into memory. If there is a hit, you can remove the common forms etc... and build them into separate .app files to avoid that hit.

>Hi Charles,
>
>Thanks...I can see that working (before I even try); I wonder though what kind of hit to memory will happen loading such a large file as a procedure (ie. 8 MB) but maybe VFP still works like the old, old, old FoxBase 2.1 where they used to advertise the product as an "incremntal loader" ie. procedures were not actually loaded in memory until needed. In that case, probably only a skeleton of what is in Mk.exe is loaded as part of the procedures list.
>
>And no, I did not just upgrade to VFP from FoxBase 2.1, I just have a good memory <grin>.
>
>Thanks again, Albert
>
>>

>>SET PROCEDURE TO mk.exe ADDITIVE  &&or put this in your startup code
>>DO FORM AskDates
>>RELEASE PROCEDURE mk.exe  *optionally
>>