(You should already have read most of the file YourFile, about .htaccess files and their value and uses; if you haven't, please do so before reading this document.)
The .htaccess file is a configuration file found on Apache-powered servers. Servers running, for example, Microsoft server software do not have an .htaccess file, nor any close equivalent. You will by now have read some of the amazing things your .htaccess file allows you to do on an Apache server.
Microsoft, in designing FrontPage, opted to call certain of FrontPage's many private configuration files ".htaccess"; FrontPage typically strews several files of that name across the directories of a web site on which it is being used. Moreover, FrontPage frequently rewrites those files, and--the crux--will cease to function, claiming it cannot access the site, if any real Apache .htaccess configuration lines are put in a FrontPage-generated .htaccess file.
Two points. First, while there is some disagreement among the sources on the web as to whether any normal .htaccess instruction breaks FrontPage or only certain ones (and I am not in a position to experiment, as I do not use FrontPage, or any file-creation tool beyond a text editor), it is universally agreed that redirection absolutely, positively cannot be made to work from a FrontPage htaccess file. So are you dead in the water for this package? By no means: stay tuned.
Second, though what matters is the effect not the cause, reasonable minds can have little doubt that this was a coldly calculated and deliberate move on Microsoft's part to use a popular piece of their software as a tool to seriously cripple the usefulness of a highly popular non-Microsoft server type. There was no need in the world for them to give their private config files the highly unusual and particular name ".htaccess" save to make real .htaccess files--with all the power they give Apache users--unusable.
But this package does not require you to change your software or your work habits.
First of all, if you do not use FrontPage's "publish to server" option--that is, if you use "publish to file" to do all your work locally (on your computer) and then just ftp-upload the results, you have no problem--you can just go ahead and follow the regular install instructions for this package, so let's just return to the YourFile document.
If you do use "publish to server" (and thus the so-called "FrontPage Extensions" as supplied by your ISP), then what you need to do is keep two distinct root-directory .htaccess files and swap them out before and after a FrontPage editing session. More exactly: as a one-time effort--
You can now use your web site as a normal Apache-hosted site, using the full power of your .htaccess file. But . . . when it is time to do a FrontPage edit of your site, you need to do these things:
You can resume normal operation. Do be aware that for the period you are using FrontPage (that is, while the FrontPage .htaccess file is in place) your users will be unable to use your fine new bookshop: if they click on a title, they will get a 500 Error report because your FrontPage .htaccess file cannot redirect their URL calls to the php script.
I say again that if this is you, you should give very, very serious consideration to using FrontPage in the way most experts seem to: do your editing locally, then ftp-upload the resulting page files. I'm not asking you to take my word for it: Google around on the topic.
Anyway, all that will be found to be faster and easier to do than to describe (you could probably write a simple script to automate the swapping in and out). Now let's return to the YourFile document.