Maintaining off-document connectivity

[Scott Clarke]

I'm an intern working on a project for a company that wishes to split their
process flows into separate but cross-linked software-specific and
hardware-specific documents so that the main document does not require
updating as often. The intent is to have this functional as a group of Visio
documents, sorted by application.

I am using Visio 2003 Professional SP1 on Windows XP. I am using
RUNADDONWARGS("OPC","/CMD=4"), and I have also set the hyperlinks to relative
path. The links do work when the absolute path is used. I have tried this
both locally and on a network drive.

Using one of my links as an example, the main document is in folder "Main\"
and the other document I wish to link to is
"Main\Fleet\Process\Software\Confirm RWT.vsd". I started by navigating to
the files normally in the OPC dialog and then changing the hyperlink address
field and User.OPCDDocID field to "Fleet\Process\Software\Confirm RWT.vsd"
This did not work, so I tried "..\Fleet\Process\Software\Confirm RWT.vsd" and
"\Fleet\Process\Software\Confirm RWT.vsd", all to no avail.

What do I need to do to get this working?

 

[Paul Herber]

On Tue, 5 Aug 2008 11:54:00 -0700, Scott Clarke <Scott

I'm an intern working on a project for a company that wishes to split their
process flows into separate but cross-linked software-specific and
hardware-specific documents so that the main document does not require
updating as often. The intent is to have this functional as a group of Visio
documents, sorted by application.

I am using Visio 2003 Professional SP1 on Windows XP. I am using
RUNADDONWARGS("OPC","/CMD=4"), and I have also set the hyperlinks to relative
path. The links do work when the absolute path is used. I have tried this
both locally and on a network drive.

Using one of my links as an example, the main document is in folder "Main\"
and the other document I wish to link to is
"Main\Fleet\Process\Software\Confirm RWT.vsd". I started by navigating to
the files normally in the OPC dialog and then changing the hyperlink address
field and User.OPCDDocID field to "Fleet\Process\Software\Confirm RWT.vsd"
This did not work, so I tried "..\Fleet\Process\Software\Confirm RWT.vsd" and
"\Fleet\Process\Software\Confirm RWT.vsd", all to no avail.

What do I need to do to get this working?

Does it not work with the full relative path
"Main\Fleet\Process\Software\Confirm RWT.vsd" ?

 

[Scott Clarke]

No, it still can't find it.

 

[Scott Clarke]

Just in case anyone wants closure on this, I managed to contact a member of
the Visio team and he informed me that the off-page connector feature does
not support relative links.

 

[Paul Herber]

On Thu, 7 Aug 2008 07:49:02 -0700, Scott Clarke <Scott

Just in case anyone wants closure on this, I managed to contact a member of
the Visio team and he informed me that the off-page connector feature does
not support relative links.

What about ordinary hyperlinks? They can do relative links.

 

[Scott Clarke]

The ordinary hyperlink is the solution I have been using.

When editing the files, I use a batch file to subst their container folder
to Q:, then when I save it, I run a VBA script to make the hyperlinks
generated relative by replacing "Q:\" with the appropriate number of "..\" s
That way it's easy to navigate both for editing and viewing. I added a
SendKeys("{F5}") under Document_DocumentOpened for all the documents, as well
as a few commands to close the document linking to it. So far the response
has been positive.