Sarah wrote in part: >> The error message translates to "can't find stack". In the standalone settings, do you refer to any other stack? Are you using any externals and if so, do you have them for all the platforms you are building for. <<
Thanks for the quick response, Sarah. This project has always been a single stack with no substacks and no externals. The single stack is the only item listed in the standalone builder. >> However, a build time of more than 2 hours seems to indicate that something is seriously wrong. While I have never tried to compile a stack with 450 cards, I have built apps with a lot more than 9 MB and they take less than a minute to build. << The standalone build time may have to do with the number of controls, which is in the thousands. It didn't always take this long; it's grown with the stack. Because I've watched the build time lengthen gradually as I've worked on the stack, it isn't so alarming to me. But the error message is quite alarming, because it stops the entire show. I have done a lot of work since my last standalone build, so I have no way of knowing what events may have created this. >> Are you using "Search for required inclusions" or do you select the required inclusions yourself? << I select the required inclusions myself: "Ask" and "Answer" dialogs and "Cursors." Each time I attempt a build, the error message appears at about the same time into the build. This makes me think it may be glitching on something in one of the cards. A long time ago, with a different project, I had a problem with my builds stopping in SuperCard. In that case, it was easy to diagnose, because the SuperCard standalone builder displayed the card and control it was working on as it made its way through the stack. The build bombed out each time it reached the same button on a certain card. Because the details were frozen in the standalone text field, I knew where the problem was. I went to the card, replaced the button with a fresh one, and the stack built fine from then on. The builder didn't like something about that button. The Revolution builder, on the other hand, gives no indication as to exactly what it's working on. If I'm again experiencing the same kind of problem, it's going to be difficult to find in a stack this size (a needle in a Rev stack). The only reference point I have is that it's happening about two hours into the build. At this point, I am doing this: I created a brand-new stack, and I started pasting cards from the old stack into the new stack. The new stack does build a standalone successfully. However, I want to avoid reconstructing the entire stack in this manner, because I noticed that the ID's of the controls change when the cards are pasted into a new stack. I do have ID references within the stack, and I don't want to create unforeseen problems in a large stack that I very carefully checked as I built it. Also, if there is a bad control somewhere, I will have to do very frequent builds to track down its location. At two hours per build, that could take a long time. At the same time, it may be a totally different problem. Do you have any other ideas or suggestions? Thanks, Ted _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution