You're almost there.

You need to get a better understanding of relative links.

Here's a (cheesy but simple) tutorial about it: http://www.compugoddess.com/relvsabs.htm

Here's another one: http://www.boogiejack.com/server_paths.html

So, if you have two lessons, and each is inside their own folder (lesson1, lesson2) and you want lesson1 to link to lesson2 at the end, then your link needs to look something like this: ../lesson2/lesson2.html

The ../ says "go up one level, then find a folder called lesson2, go inside this folder and find a file called lesson2.html to open.

Does this help?

Relative paths do not use drive letters.  They state the path to the next one "relative" to the current one.

In your example, if project1 is going to open project2.html then the relative link will look like ../project2/project2.htm

Note that I'm using forward slashes / not backslashes \ as you had.  The reason for this is that when you are delivering content to web browsers over intranets or internets the file paths always use / .  If you are working in Windows Explorer (not Internet Explorer) and displaying file paths on a computer drive or network LAN you use backslashes in paths.  If you have your link set to use backslashes, it may work fine on your own PC but then break when you upload it to some web servers that don't like backslashes in links.

I've just tested this link on my own PC and it worked fine.

One extra thing you may need to check carefully is that you quote the filename as HTM not HTML.  Captivate generates HTM files. If you set the link to look for HTML it will break and give you an error.

Do you get an error message appear at all when your first project tries to open the second project?

If so, attach a screenshot of this error.

Just a note to thank you for this thread.  Your problem may not be solved, but the thread has given me some ideas...

Thanks!

The same thing happened to me - ends at Project 1.  I haven't tried it further, though.

Hello Rod.

Your three projects chain successfully on my local machine where I have administrator privaleges, in either Firfox or Internet Explorer.

My challenge is how to create the appropriate scorm package to upload them to the LMS, and get them to work there.

Cheers.

Gerard

@Rick.  I just went and checked the Start and End settings in the project1.cptx file and you were correct that it was just set to Close Project.  But I think this must have been because I didn't save changes in that file before closing it down.  I DID actually publish the project1 file with the setting to Open URL at the end.  So on my system all the published files daisy chain perfectly.

Anyway, it looks as though we've found the culprit to be the Flash Security settings as you had suggested before.

Whew!

Can we add this specific fix to that list of issues you keep directing people to?

Are you trying to get one Captivate published executable to open another published executable?

Daisy chaining is most often used  with HTM/SWF content.  Each published chapter calling the next one on exit.  However, users report mixed success, and the issues usually seem to relate to browser or file folder security issues, plus Flash player security issues, interfering with the daisy chaining, especially when the content is being run from a network drive or CD ROM.

In my experience, daisy chaining is most likely to be successful when run from a web server as HTM/SWF content, not as EXE.

If you have 10 chapters of simulation it is highly unlikely that the user will want to just sit there and watch all of this in a single sitting.  So while daisy chaining might be one option, I think the better approach would be to have a menu or Table of Contents that allowed the user to navigate your lessons.

Have you considered using the Captivate Aggregator to bundle up all lessons with a combined TOC?  If you need the content to play full screen, you can try setting the HTM publish option to Fullscreen.

I think you'll find that the EXE output is more designed for single standalone lessons than for multiple lessons intended to be viewed as a daisy-chained set.  Plus, EXE files can run into lots of issues due to virus checkers, and other security restrictions.

Hi there,

I've been reviewing this posting to see if I might find a solution to a problem I've been having using daisy chaining for a project I've created in training mode. I was able to successfully use daisy chaining for a project I created in demonstration mode, but in training mode (so there's pretty much a text entry or click box on each slide), it looks like on the last slide of the first project, I have to set the click/text entry box to open another project on success... not just select this option from the end settings. This works when I'm completing the interaction in the project, but if I try to advance forward using the playbar, the last slide of the first project freezes and does not load the second project. I would like the user to be able to use the playbar to seemlessly move forward to the next project. Is there a workaround for this? Thanks for any help you might provide. I am using Captivate 5.

Hi, thanks for the quick response. Yes, I did have the preferences for the first project to set up to open another project. The problem was that the very last slide of the first project had a click box on it ... so you gave me an idea. I just duplicated the last slide and removed the interaction from the last slide and like you suggested, made the last slide very short. This way the user can use the playbar to move ahead, or if they are completing the interaction, the last slide is so short that it proceeds to the next slide with interaction (the first slide of my second project) without any hesitation. So, thank you!

If not, try this:

1. Browse to http://www.macromedia.com/support/documentation/en/flashplayer/help/se ttings_manager04.html
2. Add the folder location of your published Captivate files to the Trusted Locations list
3. Now try and play the daisy chaining example above again. 
4. If the issue preventing it from working before was related to Flash Player security settings, it should now work.