When working with Captivate projects, there are three areas of your project where names are particularly important, and they are often confused: project names, files names and project titles.
File Name
The file name (name.cp) is the name you assign your project at the time the project is created and saved for the first time (or renamed via File > Save As).
While file names can contain spaces, I recommend that you not use spaces. Why? It's not that spaces in file names cause a problem in Windows–they don't. Because the file name you assign your project is automatically reused as the project title, avoiding spaces in file names means project titles that won't have spaces (unlike file name, spaces in project titles are a potential problem). If you need a space or character between words in a file name, consider using underscores instead.
Project Title
The project title is the name you assign your published SWF, Skin SWF and HTML files when you publish your project. By default, Project Titles match the File name you assign your project when you saved it to your hard drive (or renamed it via File > Save As). The title should never, ever contain spaces. If you were to use a space here and publish SWF content, you'd end up with output files (including an HTML file) that contain spaces. When posting content to a Web server, file names with spaces cause myriad problems including link and server errors.
Project Name
If you choose Edit > Preferences and select the General category, or choose Project > Skin and select the Info tab, you can give your project a name. Often confused with the project's File name and title, the project name can, and should contains spaces. If you publish SWF content, the project name will appear in the title bar of the Web browser window when customer's open your eLearning lesson.
Do you have a Captivate production problem that's making you pull your hair out? Email your problem and let others learn solutions from your experience.
I just started using this yesterday. I’m trying to link two projects together as my main project is quite large. I’m using a button (on success – open other project). I followed the directions in the help, but when I click the button, it opens IE to the page “http://dmexcel_demo.htm/” but says it does not exist. ‘dmexcel_demo.cp’ is the name of my sub-project. Both project files (.CP) are in the same folder. I published the dmexcel_demo, but the HTML is in a subfolder. When selecting the ‘project’ in the button properties, I also tried selecting the .swf file that is in the same folder as the htm, but it’s not changing the behavour.
What am I missing?
I just started using this yesterday. I’m trying to link two projects together as my main project is quite large. I’m using a button (on success – open other project). I followed the directions in the help, but when I click the button, it opens IE to the page “http://dmexcel_demo.htm/” but says it does not exist. ‘dmexcel_demo.cp’ is the name of my sub-project. Both project files (.CP) are in the same folder. I published the dmexcel_demo, but the HTML is in a subfolder. When selecting the ‘project’ in the button properties, I also tried selecting the .swf file that is in the same folder as the htm, but it’s not changing the behavour.
What am I missing?
I just started using this yesterday. I’m trying to link two projects together as my main project is quite large. I’m using a button (on success – open other project). I followed the directions in the help, but when I click the button, it opens IE to the page “http://dmexcel_demo.htm/” but says it does not exist. ‘dmexcel_demo.cp’ is the name of my sub-project. Both project files (.CP) are in the same folder. I published the dmexcel_demo, but the HTML is in a subfolder. When selecting the ‘project’ in the button properties, I also tried selecting the .swf file that is in the same folder as the htm, but it’s not changing the behavour.
What am I missing?
When creating the link to the project, pay particular attention to the name of the project that you’re linking to. When you publish that project, its name MUST match the name it had when it was linked to… otherwise, the external links won’t work. If you’re thinking that this is a pain, you are correct. That’s why we avoid external links to projects and rely on a menu instead.
When creating the link to the project, pay particular attention to the name of the project that you’re linking to. When you publish that project, its name MUST match the name it had when it was linked to… otherwise, the external links won’t work. If you’re thinking that this is a pain, you are correct. That’s why we avoid external links to projects and rely on a menu instead.
When creating the link to the project, pay particular attention to the name of the project that you’re linking to. When you publish that project, its name MUST match the name it had when it was linked to… otherwise, the external links won’t work. If you’re thinking that this is a pain, you are correct. That’s why we avoid external links to projects and rely on a menu instead.