When I go to publish, I get a message about exporting the files related to these clickboxes. Then after publishing, the links don't work.

What am I missing?

Hi there

The message is really more of a simple advisory that reminds you to be sure
and copy any linked files to the same folder as your Captivate content.
However, links to .PDF and .DOC files frequently fail from Captivate. I'm not
sure why, but I do have a workaround I've developed. That workaround involves
using the companion MenuBuilder application to create a .SWF that is invisible
and only opens the desired file. In MenuBuilder you insert a Click Box and
configure it to open the file. You export that from MenuBuilder as a .SWF, then
drop it into a Captivate slide as an animation. Then place it over an image of
a button or some other cue that alerts the user they may click to open it.

When you do this, Captivate will tell you that something is referencing root.
That's a simple advisory and can be safely ignored.

Hopefully this was helpful... Rick :smile;

In my experience, the default method of including links to documents
fails in Captivate (just as it does in Adobe Presenter, i.e. Breeze).

Relative paths to documents fail when published as Flash format and accessed
on a web server. However, full (or absolute) paths seem to work. So, in
Captivate when you select to link to a document from a button or click box, you
can still use the "browse" feature to find the document. But then, you should
edit the path it creates by putting in the full URL to the document that will
be appropriate once it's staged to a web server. For example, instead of
.../documents/myfile.pdf you should use
http://www.mydomain/documents/myfile.pdf. This of course won't work for local
testing on your PC, but it will once all files are staged to your web server.

[q]Originally posted by: Captiv8r
Hi there

The message is really more of a simple advisory that reminds you to be sure
and copy any linked files to the same folder as your Captivate content.
However, links to .PDF and .DOC files frequently fail from Captivate. I'm not
sure why, but I do have a workaround I've developed. That workaround involves
using the companion MenuBuilder application to create a .SWF that is invisible
and only opens the desired file. In MenuBuilder you insert a Click Box and
configure it to open the file. You export that from MenuBuilder as a .SWF, then
drop it into a Captivate slide as an animation. Then place it over an image of
a button or some other cue that alerts the user they may click to open it.

When you do this, Captivate will tell you that something is referencing root.
That's a simple advisory and can be safely ignored.

Hopefully this was helpful... Rick :smile;[/q]

It does, but I don't understand the part about including the files in the
output folder. I'm outputting as an exe. There is no output folder.

[q]Originally posted by: Captiv8r
Hi there

The message is really more of a simple advisory that reminds you to be sure
and copy any linked files to the same folder as your Captivate content.
However, links to .PDF and .DOC files frequently fail from Captivate. I'm not
sure why, but I do have a workaround I've developed. That workaround involves
using the companion MenuBuilder application to create a .SWF that is invisible
and only opens the desired file. In MenuBuilder you insert a Click Box and
configure it to open the file. You export that from MenuBuilder as a .SWF, then
drop it into a Captivate slide as an animation. Then place it over an image of
a button or some other cue that alerts the user they may click to open it.

When you do this, Captivate will tell you that something is referencing root.
That's a simple advisory and can be safely ignored.

Hopefully this was helpful... Rick :smile;[/q]

It does, but I don't understand the part about including the files in the
output folder. I'm outputting as an exe. There is no output folder.

Hi again

Well it's quite simple. Even if you are creating a .EXE file, it has be
created in a folder *somewhere* on your hard drive, right? What is meant is
that you need to ensure the .PDF or .DOC file exist inside the same folder as
the .EXE file. Wherever that may be.

Cheers... Rick :smile;