[Timothy D. Ginn]

Here's a few more reasons against frames:

Not very search engine friendly
Makes it difficult to bookmark specific pages within your site to easily return to
What happens if someone stumbles onto a page intended to be just a content frame and your navigation is in another one? ...confusion.

Also, here's a solution to a common problem:

For those looking to frames for an easy way to have standard navigation, take a look at SSI (Server-Side Includes). The free services are more likely to support them than they are to support a full-fledged language like PHP or ASP. It makes it easy to include a standard navigation menu, example:

<!--#include virtual="/navigation.txt" -->

Also, for those who do have access to PHP, you can set an option in the php.ini, httpd.conf, or .htaccess file to allow a common header and footer to be added to your pages.

Here's an example of how you would do this in a .htaccess file:

php_value auto_append_file "header.txt"
php_value auto_prepend_file "footer.txt"

There's an easy way to do the same thing in ASP, too. (I'm not quite sure what it is, off hand, but it shouldn't take too long to look up)