FP2000: Image Maps Used With Include Pages Does Not Retain Hotspot Integrity

When an image map occurs on a page that has an Include page and within the Included page itself, one of the image maps will not function properly when viewed in the browser.

When image maps are constructed automatically in FrontPage using the image map hotspot tools, FrontPage will automatically give the image map names of the form "FPMap0", "FPMap1", "FPMap2", etc. When a single page contains multiple image maps, FrontPage ensures that all the image maps have unique names. However, when one page with an image map includes another page with an image map, the image map names may conflict and one will not work correctly when viewed in the browser.

A workaround to this issue would be to manually rename the image maps in the include pages, using unique names that do not occur in any page the image map is included in. To do this, open the included page in FrontPage and click on the HTML tab of FrontPage. The image map name occurs in two places - it is defined in the <MAP> tag and then referenced in the <IMG> tag. The name needs to be changed in both locations.

See samples below:

Before:
After:

To resolve this problem, obtain Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a).

To obtain SR-1/SR-1a, click the article number below to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.