It would also behoove Google to document what: <gs:options allCols='false' allRows='false'/>
is doing in the table <entry/> of late. (although I'm not sure I'd do it like that, myself ... supplying <gs:column/> and <gs:data rowCount=x"/> become even more nonsensical in the presense of <gs:options/>). There was a hint in the ss 3.0 developer guide that specifying: <gs:data numRows="0" /> would give us all rows in the sheet. (Although this seems not to be the case at the moment). In practice, managing the table size/height is annoying. I have taken the approach to always check the worksheet's actual dimensions against the table's definition (and to resize/recreate the table if necessary), since there are zero committments made by the docs concerning how the table does or doesn't grow/shrink as rows are inserted/appended to the sheet via various API's If you guys have a strategy regarding table definitions, it would sure be nice to hear about it. We have an opinion. cheers, David.
