FrontPage Help
Split or merge frontpage tables
FrontPage behaviors and layers
FrontPage extensions can and do become corrupt.
Often this is caused by the web site owner! If you suspect your extensions to be corrupted or broken, you simply un-install them and re-install via your web hosting control panel. I strongly suggest that you leave a few hours between the un-install and re-install. Your control panel will show that the extensions have been un-installed but the server will still be removing them. So its best to wait or you will never properly fix them.
The following components require the FrontPage 2002 Server Extensions:
File Upload Custom link bars, Shared border background properties, Usage analysis reports, Top Ten List Web Component, New security features (user roles) FrontPage 2000 Server Extensions Components
Nested subwebs, Lightweight Source Control (document check-in/check-out without Microsoft Visual SourceSafe for Windows) Categories component, StyleSheet links to multiple files or Active Server Pages (ASP) files, FrontPage Server Extensions Components
Confirmation field, Discussion form handler, FrontPage-created server-side image maps, Hit counter, Registration form handler, Save Results form handler, Search form Field set.
The most likely cause for broken or corrupt FPSE is the use of FTP (file transfer protocol) If you have installed FPSE, then you should publish your web site with the FrontPage publish tool (http) if you have installed FPSE and then try and publish your site via FTP, you will break the extensions! Whilst you might succeed in publishing your web site, you will loose the functionality of those components that rely on FPSE to work. This include FrontPage forms. In some extreme cases, you may need to request that your host re set the extensions for you. Your host can do a complete re-install and fix certain things that cannot be done via your control panel.