Microsoft KB Archive/172287

= ACC97: Error When Clicking Page Link in Report Exported to HTML =

Article ID: 172287

Article Last Modified on 1/20/2007

-

APPLIES TO


 * Microsoft Access 97 Standard Edition
 * Microsoft FrontPage 97 Standard Edition
 * Microsoft FrontPage 1.0 Standard Edition
 * Microsoft FrontPage 1.0a
 * Microsoft FrontPage 1.1 Standard Edition
 * Microsoft FrontPage 1.1a

-



This article was previously published under Q172287



Moderate: Requires basic macro, coding, and interoperability skills.



SYMPTOMS
When you export a report to HTML format, and then view the report in your Web browser, you may receive one of the following error messages when you click on one of the page links:

HTTP/1.0 500 Server Error (161)

  -or-

HTTP/1.0 400 Bad Request



CAUSE
You edited a template in Microsoft FrontPage, and then you used that template when you exported the report to HTML.



RESOLUTION
After you have edited the template in Microsoft FrontPage, open it in a text editor, such as Notepad. In the tokens that create the navigation links, replace any instance of the string "%3c" with the character "<"; replace any instance of the string "%3e" with the character ">" as well. For example, change

First

Previous

Next

Last

to:

First

Previous

Next</a>

Last</a>

After you have saved the edited template, export the report to HTML again.

You can also edit the HTML files to which the report was exported and add the hyperlinks that allow you to move to different pages. For example, on the first page of the exported report, the navigation hyperlinks would be:

<A HREF = "#">First</A>

<A HREF = "#">Previous</A>

<A HREF = "Report1_1Page2.html">Next</A>

<A HREF = "Report1_1Page5.html">Last</A>

However, this method is not recommended because it is inconvenient if the report contains more than a few pages.

<div class="status_section">

STATUS
Microsoft has confirmed this to be a problem in Microsoft Access 97. This problem no longer occurs in Microsoft Access 97 Service Release 1.

NOTE: Stand-alone Microsoft Access 97 Service Release 1 is not currently available, but you can update your copy of Microsoft Access 97 to Service Release 1 by downloading Microsoft Office Service Release 1 from Microsoft's Web site at:

http://office.microsoft.com/en-us/assistance/HA010449921033.aspx

<div class="moreinformation_section">

Steps to Reproduce Problem
<ol> <li>Start Microsoft Access and open the sample database Northwind.mdb.</li> <li>On the Help menu, click Contents And Index and search for "HTML documents, template files," and then display the topic "HTML template file example."</li> <li>Select all of the text in the topic.</li> <li>Start a text editor, such as Notepad.</li> <li>Paste the text from the Help topic into the text file.</li> <li>Save the file under the name FPTest.htm in the \Templates\Access subfolder of the Microsoft Office folder. The default location of this folder is

\Program Files\Microsoft Office\Templates\Access</li> <li>Start Microsoft FrontPage.</li> <li>On the Tools menu, click Show FrontPage Editor.</li> <li>Open the file that you saved in step 6.</li> <li>On the File menu, click Save As. Click As File and save the file as FPTest2.htm.</li> <li>Quit Microsoft FrontPage and switch to Microsoft Access.</li> <li>On the File menu, click Save As HTML.</li> <li>In the first screen of the Publish To The Web Wizard, click Next.</li> <li>In the screen which asks what you want to publish, click the Reports tab and select Products By Category; then, click Next.</li> <li>When prompted for an HTML template, click Browse and locate the file FPtest2.htm that you created in step 12. Click Select, and then click Next.</li> <li>In the next screen, select Static HTML, and then click Next.</li> <li>When prompted for a location to publish to, choose a directory that has Read access. Click Finish.</li> <li>In a browser, enter the address of the output file you created in step 17, for example:

http:// / /Products by Category_1.html

</li> <li>Click Next to move to the next page. Notice that you receive one of the errors described in the "Symptoms" section.</li></ol>

<div class="references_section">