Exporting linked files into published .exec

Question

I have a problem in exporting any linked files I have added
as click boxes into the published .exec file.
In my project I have linked HELP pages where relevant and
inserted the URL link into the click box. It all works great when I
am on my network, but once off, the linked files are not there.
When publishing the project, a popup box says that I need to
"copy all referenced files and projects with their
corresponding HTML files to the output folder". But I do
not know how to do this.
HELP
Cheers

Answer 1

quote:
Originally posted by:
Captiv8r
All that dialog is telling you is this:
You have created links to other content. This content may be
a simple URL, Word Document, PDF, etc. Captivate is not going to do
anything to ensure those files exist when you copy the Captivate
files to wherever you will run them from. So be sure you take care
to copy the linked content to the locations where the Captivate
output will expect to find them. Otherwise, the links are going to
fail!
Hopefully this was helpful... Rick
Rick -
Let's revisit this question, please?
In my scenario, I created a button linking to a PDF reference
file. I put the file in the same directory as the final Captivate
published .exe file. The problem is that Captivate is holding onto
the logical path to the file, which works great if everyone is on
my network or computer.
No matter what you do, once you take those files off your
computer/network and hand them to a customer, any links to local
file contained on the delivery medium is broken.
For example, the .exe, reference PDF, and menu are burned to
a CD and delivered to the customer. and the customer is running the
.exe but when he attempts to open the PDF, nothing happens. Of
course, I pop the CD in and it works great for me - because I can
see the path to the published location, prior to burning the CD.
We notice that accomplishing the same action in the menu
builder doesn't produce the same result: The user can open the file
contained on the delivery medium just fine. That code seems to
recognize the virtual path rather than the logical one.
I think this is a bug in the software. Captivate is designed
to be able to publish standalone files. By definition, standalone
means that the links to external files should not be dependent on
the hard path.