Hi rf (and Adrienne):
Let me screw up my newbie courage over the next few days.
btw, here is a bit more iof the buckets of css that are involved:
table#fixedheader {
width: 790px;
table-layout: fixed;
}
/* I forgot to duplicate the above css for the t1 table and will try it
tomorrow, and determine if there's any difference */
While I get ready provide the url, here's the relevant portion in the <body>
of the page:
*******************************************
<div id="headerrow">
<table id="fixedheader">
<thead>
<tr>
<th align="center" width="8%" ><u>Org ID</u></th>
<th align="center" width="40%"><u>Org Name</u></th> <!-- would
like to click/sort this column -->
<th align="center" width="25%"><u>Municipality</u></th>
<th align="center" width="5%" ><u>Rgn</u></th>
<th align="center" width="22%"><u>Notable Postings</u></th>
</tr>
</thead>
</table>
</div>
<div id="tableselect">
<table id="t1">
<tfoot>
<tr>
<td align="center" width="8%" ><u>Org ID</u></td>
<td align="center" width="40%"><u>Org Name</u></td>
<td align="center" width="25%"><u>Municipality</u></td>
<td align="center" width="5%" ><u>Rgn</u></td>
<th align="center" width="22%"><u>Notable Postings</u></th>
</tr>
</tfoot>
<tbody>
<!-- My cgi server (Apache on an older Dell machine on the desk
beside me) builds the many rows, and replaces the variable #forgoptions#
below with (up to) thousands of <tr> rows. Then send the page onward to the
user -->
#forgoptions#
</tbody>
</table>
</div>
**************************************************************
Also, I'm working hard on cleaning up the database now. It currently
has 21000+ rows, and I have to cut this back a bit.
It would be unusual (but possible) for my users to request the 20,000
rows by selection from ALL Regions. I would expect the loading time on their
machines to be as slow as my tests have shown --- e.g., about 2 1/2 minutes
for loading. So, Region requests should normally be less than 2000 rows..
-Mel Smith