With frames, you are create sub-windows, each of which may have it's own content and even scroll independently.
It may sound as though frames are always better than tables, but that is not the case. Many people prefer the appearance of a page that uses tables since it is unbroken and scrolls as a single unit.
Frames may also confuse beginning users who mistakenly assume that clicking on a link took them to a new page rather than just updating one frame. The behavior of the browser "back" button may confuse them, and, if they save a page as a "favorite," they may not come back to the view they thought they had saved.
Here is an artificial example of the use of frames. If you View Source for the page, you will see the definition of a frameset with two rows and three columns:
This defines six independent pages (f1.htm, f2.htm, etc.). To see the source on the individual pages, place the mouse over the frame, right click, and View Source.
The example shown above is contrived to illustrate the frame tags. This is a more realistic example
This defines a two row frameset. The first row is 15% of the screen, and contains the document title.htm. The second row contains another frameset. This frameset has two column frameset. The first column contains a frame with the table of contents, the second is the target for the articles.