standalone maker behavior

[J. Landman Gay]

Mark Swindell wrote:
> Indeed I did.  But I thought the inclusions were included before the 
> engine was attached.  Not so?

Oops, I missed that part, sorry. Yes, inclusions should be scanned 
before the engine gets attached, so that may not be the problem.

In that case, all I can suggest is the generic checklist, some of which 
you've already ruled out:

1. The path to the stack contains non-ASCII characters, such as 
diacritical marks or accent marks.  Avoid the use of accented or 
non-ASCII characters in path names.

2. The standalone builder is set to search for inclusions but the stack 
is password protected. Select the inclusions manually instead, or remove 
the password and have the standalone builder set it during build time.

3. Alternately, the standalone builder may be having trouble searching 
for the required inclusions regardless of password protection. Turn off 
"Search for required inclusions" and turn on "Select inclusions for the 
standalone application." Then choose the resources you need to include 
yourself in the Standalone Settings dialog.

4. The folder name is the same as your standalone's name. You need a 
unique folder name; make sure you select an empty folder with a name 
different from the standalone's name.  If you have previously built a 
standalone from the same stack, do not try to build a new one into the 
same folder. Trying to overwrite an existing standalone with a new one 
can cause problems. Rename or remove the old folder first, and then 
build. (Fixed in more recent versions of Revolution.)


5. Your source stack's file name does not use an extension, or uses an 
incorrect extension. Make sure your stack's file name ends with the 
extension ".rev"

6. Your source stack contains duplicate "message box" or "ask" or 
"answer" dialogs. Remove the embedded stacks and let the standalone 
builder add them instead. (This usually only occurs with stacks 
originally created in MetaCard.)



I think the folder name business has been fixed, so #4 probably isn't an 
issue any more. I've been bitten by the ".rev" problem in the past though.
-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com