This article was previously published under Q230712
This article has been archived. It is offered "as is" and will no longer be updated.
This article describes how to use FrontPage components, which reference the Shtml.dll file, on ASP pages.
NOTE: You may receive the following error when submitting a search or submitting from a form:
Cannot run the FrontPage Server Extensions' Smart HTML interpreter on this non-HTML page: "http://servername/subweb/default.asp"
This functionality has been disabled for all versions of the Server Extensions after version 220.127.116.115 because it is a very specific security threat.
For additional information, see the following article or articles in the Microsoft Knowledge Base:
182125 FP98: Browsing to ASP Files Through Shtml.dll Displays ASP Code
You can use a server-side include to enable this by performing the following steps:
Create a .html page with the FrontPage component that you want to use on it.
Save the page.
In FrontPage, right-click your .asp page and click Open With.
Highlight Notepad and click OK.
Insert the following code on the page where you want the component to appear:
Where path is the path to the .html file with the component and filename.htm is the file you created with the component on it.
Note: This code must be in the body of the page.
Save the .asp page.
Now when you browse to the .asp page, the .html file will be included dynamically and the component will function properly.
You will notice when you submit a form from this type of arrangement that the link on the confirmation page linking back to the form does not display the original .asp page. This is because the form is actually being submitted from the .html page containing the component. As a workaround for this, you can use a custom confirmation page. On the custom confirmation page, you can make a hyperlink back to the original .asp page.
If you are using a search component, the results page will not include the contents of the original .asp page for the same reason as above.