Linking Several Project Files as one Learning Session

Question

I have eight large Captivate files that I want to link into
one, single window, seamless learning experience. I've tried quite
a few options, but I can't get any to work. In one failed attempt,
I wanted to publish 8 flash files that were linked so they would
play in Adobe Flash player together. Here are the issues I
encountered with just this option:
Tried to link Part 1 and Part 2 together using the "Open URL
of file" option and referencing the ".swf skin" file. Part 1 plays
back great, but part 2 opens up in Internet Explorer instead of
Adobe Flash Player (very annoying).
When Part 2 opens up the .swf file in Internet Explorer, it
opens up in a new window, even though I specified "Current".
When Part 2 opens up the .swf file in Internet Explorer, I
receive an "Adobe Flash Player Security" message. The first
sentence reads "Adobe Flash Player has stopped a potentially unsafe
operation."
Does anybody have any input on these three problems? I
getting frustrated that there isn't an easy way to do this. Any
help anybody could give to me would be <u>greatly</u>
appreciated.
Thanks.

Answer 1

I can't comment on the first two issues other than to say
that Captivate-generated SWF output is intended to run in a web
browser and accessed from a web server.
If you want to run directly off the local hard drive, you
should be publishing to .EXE and it should work as expected.
If you're determined to run directly in the Flash Player,
maybe try looking into something like Jesse Warren's Captivate
Player or a commercial Flash wrapper product. Google will be your
friend in this area.
However, running directly in the Flash Player rather than a
browser will ultimately be a big problem for your users, since....
The Flash Player security warning you're seeing comes up
pretty much any time you try to run Captivate-generated SWF files
directly from a hard drive, even if the SWF files are embedded in a
web page.
You, and every one of your end users, will have to click the
Settings button on the warning popup and manually mark the file
folder location as "Safe" before the content can run.
For this reason, the recommended approach is either to
publish to .EXE format for local access, which avoids the message,
or publish to HTM/SWF and host the files on a web server, where the
local Flash Player security settings do not apply.