Issues that are fixed in FrontPage 2003 by Office 2003 Service Pack 2

Microsoft Office 2003 Service Pack 2 (SP2) provides the latest updates to Microsoft Office FrontPage 2003. Office 2003 SP2 contains security enhancements, stability improvements, and performance improvements. Some of the fixes that are included with Office 2003 SP2 were previously released in Office 2003 Service Pack 1 (SP1) or in separate updates. Office 2003 SP2 combines the previously released fixes into one update. For more information about Office 2003 SP2, click the following article number to view the article in the Microsoft Knowledge Base:

Downloadable list of issues that the service pack fixes

A Microsoft Excel workbook is available that contains a list of the FrontPage 2003 issues that are fixed by Office 2003 SP2.

Note The workbook is in the English language. The workbook will not be translated into any other languages.

The following file is available for download from the Microsoft Download Center:
Download the Office2003_SP2Changes.exe package now. (http://download.microsoft.com/download/6/5/0/650783cf-ffbf-4d7b-96ce-d8dd4ab12f7b/office2003_sp2changes.exe) Release Date: September 27, 2005

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

List of issues that the service pack fixes

Issues that were previously documented in the Microsoft Knowledge Base

Office 2003 SP2 fixes the FrontPage 2003 issues that are described in the following hotfix packages:

Issues that were not previously documented in the Microsoft Knowledge Base

Office 2003 SP2 also fixes the following FrontPage 2003 issues that were not previously documented in the Microsoft Knowledge Base.

The FrontPg.exe process continues to run after you quit FrontPage 2003

You open FrontPage 2003 with an add-in that catches PageWindowEx events. When you quit FrontPage 2003, the FrontPg.exe process continues to run.


The Insert Table dialog box does not fit the 800 x 600 screen resolution

When you try to insert a table on a page in FrontPage 2003, the Insert Table dialog box does not fit on the screen. This issue occurs if the screen resolution is set to 800 x 600.


An interactive button can be dropped into a shared border

If you try to insert an interactive button when the insertion point is inside a shared border, the Interactive Button command is not available on the Insert menu. This behavior is expected. However, if you insert an interactive button on a Web page and then drag the button into a shared border, the button unexpectedly drops into the shared border.


The second row of a Data View does not contain any data

When you insert a Data View of a .xml file that contains rows of data, the second row of the Data View does not contain any data.


The underline for a hyperlink is not displayed correctly in Internet Explorer

You insert a hyperlink in a Web page in FrontPage 2003. Then, you click the Underline button to remove the underline for the hyperlink. When you view the Web page in Microsoft Internet Explorer, the underline for the hyperlink is not displayed as expected.


You cannot use the Positioning toolbar to adjust the width and the height of an image

When you try to use the Positioning toolbar to adjust the width and the height of an image, the width and the height are not changed.


You cannot press CTRL and then click an item to cancel the selection of an item in Folder List view

In the Folder List view of a FrontPage 2003 Web page, you press CTRL and then click to select multiple items. If you press CTRL and then click an item to cancel the selection of the last item that you selected, the selection of the item is not canceled. If you press DELETE, all pages that were selected are deleted.


A script unexpectedly runs on a page that contains a Data View when the Allow Rich HTML feature is disabled

Consider the following scenario. You open a Microsoft Windows SharePoint Services Web site in FrontPage 2003. Additionally, you add a multiline text box to a list and then click to clear the Allow Rich HTML check box. If you add the list as a Data View in the SharePoint Services Web site and then add a script to the Data View, the script unexpectedly runs when you open the Web page in a Web browser.


Saving a Web page that has many Web components takes longer than expected

When you save a Web page that contains many Web components, the save operation takes longer to complete than expected.


An invalid WebPartZone ID is created when you insert a Web Part Zone in a Windows SharePoint Services Web site

You open a Windows SharePoint Service Web site in FrontPage 2003. If you insert a Web Part Zone and then switch to Code view, the WebPartZone ID is invalid. For example, the WebPartZone ID may resemble the following sample: This problem occurs because the WebPartZone ID cannot start with a letter. Additionally, the WebPartZone ID cannot contain an invalid character such as a hyphen.


The attributes of duplicate code tags are saved with the same attributes on an ASP page

When you save an ASP page that contains duplicate code tags that have similar attributes in FrontPage 2003, the duplicate code tags are saved with the same attributes.


You cannot select New Turkish Lira for a currency column in a Windows SharePoint Services site

When you use FrontPage 2003 to change the currency in a currency column that appears on a page in a Windows SharePoint Services site, the only choice for Turkish currency is Turkish Lira. New Turkish Lira is not available.


A Web page that has a custom SQL statement opens with errors in a Web browser

You create a Web page that contains a custom SQL statement in FrontPage 2003. When you open the Web page in a Web browser, the Web page opens with errors.


You receive a WCAG warning message when you check a Web site for accessibility errors in FrontPage 2003

When you check a Web site for Web Content Accessibility Guidelines (WCAG) Priority 1 and Priority 2 accessibility errors and warnings, you receive an error message that is similar to the following error message: This problem may occur if a Web page contains a script that uses the <script runat="server"></script> tags.


You receive an error message after you explicitly associate a form label with a form control

When you explicitly associate a form label with a form control in the HTML code of a Web page, you receive the following error message:

FrontPage 2003 stops responding when you try to create a new WebDav Web site

You try to create a new WebDav Web site in Remote Web Site view in FrontPage 2003. When you click Yes to create the new Web site, FrontPage 2003 stops responding (hangs).


You cannot find the text in a table when you search the selected page in FrontPage 2003

You select a page of a Web site in Folder view. Additionally, the page contains text in a table. When you look for the text in the table on the selected page, you cannot find the text.


You receive error messages when you check a Web site for accessibility if XML 6.0 is installed

When you check a Web site for accessibility, you receive the following error messages: This problem occurs if Microsoft XML 6.0 is installed on the computer.

Note The accessibility check in FrontPage 2003 uses Microsoft XML 4.0 or Microsoft XML 5.0.


An accessibility check stops without errors on a page that contains a <!CDATA[]> tag

When you check the pages of a Web site for accessibility, the accessibility check stops without errors on a page that contains a <!CDATA[]> tag. Therefore, the page that contains the <!CDATA[]> tag and all the pages that follow are not checked for accessibility.


Note After you upgrade to Microsoft FrontPage 2002 Service Pack 3 (SP3) or to FrontPage 2003, custom queries must strictly follow a specific format to be processed by FrontPage. All existing custom queries that do not follow this format cannot be authored by using the Database Results Wizard after you install FrontPage 2003 SP2. If you try to edit such a query, you receive the following error message: For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Error signature details

When you use FrontPage 2003, you may receive an error message that is similar to the following: When you view the data in the error report, the report contains an error signature that is similar to one of the following error signatures.Additionally, other program versions, module versions, and offsets are possible.