Working with tables

G

gnorviel

I want to set the top row of the table not to scroll while the rows below it
scroll. This is so the person viewing the table on-line can see the labels
in the top row as they scroll down the table.
 
S

Sparky Polastri

gnorviel said:
I want to set the top row of the table not to scroll while the rows below it
scroll. This is so the person viewing the table on-line can see the labels
in the top row as they scroll down the table.

You want a "frameset" for that.
 
G

gnorviel

Any other ideas? I have many products with maybe 5 options each. It isn't
practical to create a new page for each product, so they are on tables.
 
C

clintonG

Using a Frameset is the only way to do what you want to do.
Don't listen to the pooh-pooh talk about frames. Learn to use
them correctly. Start reading what others have to say and have
learned how to work around the shortcomings.

Google: "frames"+"search engine optimization"

--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET [email protected]
URL http://www.metromilwaukee.com/clintongallagher/
 
S

Steve Easton

Place the labels in a layer.

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
M

Murray

As far as I know, the most comprehensive discussions of frames and their
potential problems can be found on these two links -

http://apptools.com/rants/framesevil.php
http://www.tjkdesign.com/resources/frames/

The biggest problem with frames is that a) they are most often chosen by the
people who are least able to deal with the many workarounds, and b) once you
start to use them you are committed to one workaround after another. In the
scheme of things, each workaround is relatively minor, but taken as an
aggregate, and compared to the fact that you have none of those problems
with flat pages, I find that frames do not pass the old Ben Franklin test.
 
M

Murray

Yep - I like it quite a bit. Gary knows his stuff, and I think he has
covered all the salient points.

The reall thing is this. The people who chose frames, by and large, are
those who are least equipped to deal with these issues. And using frames
means that you have a litany of issues to deal with.

--
Murray

clintonG said:
That apptools document [1] 'is' a very good reference Murray as it
explains which shortcomings and begins to offer solutions. Thanks.

--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET [email protected]
URL http://www.metromilwaukee.com/clintongallagher/

[1] http://apptools.com/rants/framesevil.php


Murray said:
As far as I know, the most comprehensive discussions of frames and their
potential problems can be found on these two links -

http://apptools.com/rants/framesevil.php
http://www.tjkdesign.com/resources/frames/

The biggest problem with frames is that a) they are most often chosen by the
people who are least able to deal with the many workarounds, and b) once you
start to use them you are committed to one workaround after another. In the
scheme of things, each workaround is relatively minor, but taken as an
aggregate, and compared to the fact that you have none of those problems
with flat pages, I find that frames do not pass the old Ben Franklin
test.
 
Top