What to do when building standalones goes mysteriously wrong?– try removing passwords from stacks – try toggling the destroyStack property – check whether pictures are referenced or imported as controls – make sure that pictures are in the correct location relative to your stack – make sure to use relative file paths for portability – select “Select inclusions” instead of “Search for required inclusions” on the General pane of the standalone application settings – after selecting “Select inclusions”, make sure that you actually include all components that you need for your stack, this may involve knowing for sure what each component does – you might try to forget about profiles, just select “Remove all” – if you build for multipe platforms, try building for one platform at a time – quit and restart Revolution without saving your project right after building a standalone – quit and restart Revolution after saving your project and before building a standalone – when moving your standalone for Mac OS 9 or Mac OS X to a different computer, make sure to create a sit or zip file of your standalone first – when uploading your compressed standalone or exe file to a server, make sure that your FTP software treats it as binary – you might try to build a standalone while suppressing messages (see Development menu) – you might try to build a standalone while suppressing errors (see Development menu) – if building standalones takes ages, set the cREVKeepDevelopmentProperties of your mainstack to true – Error: “A stack “answer dialog” in file (path to my stack) is already in memory. The Revolution UI does not distiguish stacks with have identical names, so editing these stack files which both are in memory could result in data loss.” When the preference “If destroyStack is false, when closing last stack in file:” is set to “Don’t close the file” then a built standalone is partially corrupted or the building process throws errors and aborts. This was not the case with version 3.5. RunRev reports: “I think this issue is related to a certain preference setting. It appears to be fixed in the development builds of the next version of Revolution which are available to our enterprise customers. However if you are using 4.0, I think the problem can be worked around by changing the preference “If destroyStack is false, when closing last stack in file:” to something other than “Ask”. This can be found by doing Edit -> Preferences -> Files & Memory.” I have no confirmation, yet.