Digital Workshop

In using the "Launch this file" option I am pointing at file 1.100 HSE.pdf. I set the "The file will be found at this location" pointer to "<SYSTEM_CD_DRIVE>\1.0 HSE" which is the directory on the CD that the pub runs from.

When I do a test from within Opus, it locates the file and runs it just fine. However, if I publish and test, it does not.

What is up with this? I tried just about every standard file convention I can thing of with no luck, including moving the file to the same directory level as the executable. Nothing.

Dave

PS - Dug through the files and located a moderator response suggestion the use of "<SYSTEM_PUBLICATION_DIR>\1.0 HSE"

Doesn't help.

Hi,

I had the same problem a few weeks ago.
What i did was creating a button with the 'launch file' function, put the PDF files on the CD and link them file to the CD using the <SYSTEM_CD_DRIVE> function. no problem


Ad

Thanks. That worked for me to...until I burnt the CD.

As it turned out, supergeekopusmaximus DemoFred had the answer. I didn't like it, but it worked. Had to change the file names. Even though they are Windows "standard," Opus didn't like it. Why they would work until compiled still eludes me...

Thanks, Fred.
Dave

Dave --

Thanks for my new title (supergeekopusmaximus). You can call me "SGOM" for short.

While Windows may accept file names with more than one period (.) and spaces ( ), when you are naming things in OPUS, I suggest only having one period between the name and the file extension, AND no spaces. Use the underline (_) to make it more visually appealing (like_this_always.txt).

Why does your naming convention (periods, special characters and spaces) work in Preview but not when you Publish? I'm not sure. Always make the assumption it won't work and your life will be simplier.