Microsoft Knowledge Base Email Alertz

KBAlertz.com: (172287) - 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

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com

ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 172287 - Last Review: January 20, 2007 - Revision: 3.4

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

This article was previously published under Q172287
Moderate: Requires basic macro, coding, and interoperability skills.

On This Page

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
<a href="http://support.microsoft.com/?scid=%253c%21--accesstemplate_firstpage--%253e">First</a>
<a href="http://support.microsoft.com/?scid=%253c%21--accesstemplate_previouspage--%253e">Previous</a>
<a href="http://support.microsoft.com/?scid=%253c%21--accesstemplate_nextpage--%253e">Next</a>
<a href="http://support.microsoft.com/?scid=%253c%21--accesstemplate_lastpage--%253e">Last</a>

to:
<a href = "<!--AccessTemplate_FirstPage-->">First</a>
<a href = "<!--AccessTemplate_PreviousPage-->">Previous</a>
<a href = "<!--AccessTemplate_NextPage-->">Next</a>
<a href = "<!--AccessTemplate_LastPage-->">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.

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 (http://office.microsoft.com/en-us/assistance/HA010449921033.aspx)

MORE INFORMATION

Steps to Reproduce Problem


  1. Start Microsoft Access and open the sample database Northwind.mdb.
  2. On the Help menu, click Contents And Index and search for "HTML documents, template files," and then display the topic "HTML template file example."
  3. Select all of the text in the topic.
  4. Start a text editor, such as Notepad.
  5. Paste the text from the Help topic into the text file.
  6. 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
  7. Start Microsoft FrontPage.
  8. On the Tools menu, click Show FrontPage Editor.
  9. Open the file that you saved in step 6.
  10. On the File menu, click Save As. Click As File and save the file as FPTest2.htm.
  11. Quit Microsoft FrontPage and switch to Microsoft Access.
  12. On the File menu, click Save As HTML.
  13. In the first screen of the Publish To The Web Wizard, click Next.
  14. In the screen which asks what you want to publish, click the Reports tab and select Products By Category; then, click Next.
  15. 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.
  16. In the next screen, select Static HTML, and then click Next.
  17. When prompted for a location to publish to, choose a directory that has Read access. Click Finish.
  18. In a browser, enter the address of the output file you created in step 17, for example:
    http://<servername>/<directory>/Products by Category_1.html
  19. Click Next to move to the next page. Notice that you receive one of the errors described in the "Symptoms" section.

REFERENCES

For more information about navigation links in templates, please see the following article in the Microsoft Knowledge Base:

164007  (http://kbalertz.com/Feedback.aspx?kbNumber=164007/EN-US/ ) Reports Exported to HTML Have No Page Links

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
Keywords: 
kbdownload kbbug kberrmsg KB172287
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please