>
> http://html-faq.com/htmlframes/?framesareevil
> http://homepage.ntlworld.com/l_vajzo...eb/frames.html
> http://www.karlcore.com/articles/article.php?id=2
> http://david.us-lot.org/www/frames/
>
Hummm? That anti-frame tirade hardly addressed the question. All good points
though, and I quit using frames on my large website long ago. However, when
I leased a discussion forum that gave me full HTML control, I decided to
consolidate my entire website and present it on the same page as the forum.
(Forum on the left, web site on the right). Tables were difficult to set up
and I had the forum controlled via CSS. However, this was not easy to do
because of the way the hosts set up the maintenance pages. I.e., you are
allotted so many k for the header, so many for the upper part, bottom part
etc. I did set it up, however, only to discover in the end that the kbs
allotted wasn't near enough for my purposes. Hence the final resorting to
the iFrame.
As one of your links says, "frames are evil (most of the time)." I agree
with this, but the iFRame in this instance filled my need admirably and
simplified the task. Without it I don't have a clue as to how I would have
accomplished this.