Hi Rod,
Thanks for your feedback. Yes, I am using the multiple SCORM modules that all belong to the same course. The LMS doesn't track the progress, though. I'll definitely try the MultiSCORM packager. The only question I have is linking the projects together. Should I use a relative path or absolute?
I've been reading about different solutions, but none of them has worked except the absolute path. On Captivate support page they say to link to the actual captivate file, but it didn't work for me. The other page was suggesting to publish the mini projects to the main published folder and use the link, which I did and it seems to work, but LMS doesn't navigate through the course. I will try the MultiSCORM packager which looks like to be the solution. I just would like to learn how to link the mini modules to the main Captivate file. I really appreciate your feedback.
When you are building SCORM objects you have to forget about the idea of pointing one SCORM directly at another to open it via any kind of path (relative or absolute).
The SCORM standard says that each SCO should be totally self-contained and doesn't link out to anything. It's expecting you to allow the LMS to provide the navigation from one SCO to the next via the LMS player or via some other Auto-Continue function that the LMS might provide.
If you build a Multi-SCORM course bundled using the Multi-SCORM Packaging tool that comes with Captivate then the LMS SCORM player should show a TOC that allows navigation to each module in that course.
AdChoices