Consider the following scenario. You use Microsoft Office Visio 2003 or Microsoft Visio 2002 to create a Web page. Additionally, you add a hyperlink to a shape on the Web page. The hyperlink links to another page in the same Visio file or to another local Visio file. Then, you save the Visio file as a Web page. When you open the Web page and then click this hyperlink, you receive the following error message: This issue does not occur when you use Hypertext Transfer Protocol (HTTP) or File Transfer Protocol (FTP) to create a hyperlink.

Note A local file is a file that is stored on your computer.

Back to the top

This issue occurs because the hyperlink that you created uses a relative path instead of an absolute path to locate the destination Visio file.

Back to the top

To resolve this issue, specify an absolute path instead of a relative path when you create a hyperlink. To do this, follow these steps:

1.	Start Visio.
2.	Open the Visio file that you want to save as a Web page.
3.	Display the page that contains the shape to which you want to add a hyperlink. Then, click the shape.
4.	On the Insert menu, click Hyperlinks.
5.	In the Address box, click Browse next to the Address box, and then click Local File.
6.	In the Save in box, locate the destination Visio file, and then click its file name.
7.	Click Open.
8.	In the Sub-address box, type the page number to which you want to link. Alternatively, you can click Browse next to the Sub-address box to specify the page number.
9.	Click to clear the Use relative path for hyperlink check box, and then click OK. Note If the Use relative path for hyperlink check box is unavailable, go to step 4. Then, click Hyperlink1 in the list, and then click Delete. Click New, and then go to step 5.
10.	Save the Visio file as a Web page.
11.	Test the hyperlink on the Web page to verify that the hyperlink works correctly.

Back to the top

For more information about how to use absolute and relative paths in hyperlinks, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top