I am currently putting the finishing touches on a MC project which we plan to put on CD-ROM. The program presents map information on Biblical sites and its size is around 10 Mb. Making it into a standalone will increase its size even more. Based on the advice shared in this list, I plan to break it into about 8 smaller stacks to reduce memory requirements and enhance speed. My plan is to make the portion containing the Main Menu into a standalone with other stacks which it can open based on the user's response. I have several questions concerning this: 1. Should each stack (portion of the original program) be its own main stack or should they be substacks of the Main Menu stack? In other words, if all the stacks are substacks of the Main Menu stack, are they all loaded into memory when the Main Menu stack is opened, thereby defeating the purpose of making them into individual stacks? Or does it matter? 2. If each stack should be its own main stack, do they each need to be made into standalones? 3. If only the Main Menu stack needs to be a standalone, does it have to always remain open even when other stacks are opened? 4. I have all the icons on a couple cards and had planned to include those cards in each substack. Will that create problems with the same icon being in each stack with the same ID number? 5. Currently, before a card is closed I push that card. Each card then includes a "return" button which will take them back to the last card by simply popping the card when the button is clicked. Since the last viewed card could be in a different substack, do I need to test for which stack it is in and open that stack before the card can be popped? As always, the help from this list has been invaluable. Philip Chumbley
