Kevin,
Your follow-up question is an interesting one. It was raised during the EAP but looking at the discussion trails that arose out of the EAP discussion, the EAP question had two parts and the focus was on the first part (an unnecessary scroll bar being rendered), and the second part about number of rows seems to have been overlooked.
If you run same program with same .4st using Windows GDC, you should see that the number of rows is fixed to that as defined in the .per. As sizable=no, you can't resize or maximise the window to make more rows appear. So it could be argued that the GBC behaviour mimics the GDC behaviour. It also matches the documented behaviour for sizable=no "On a normal window, the behavior is applied to the form instead of the window. When set to "no", the form content is not stretched, even if the form contains stretchable items."
But if you removed the position=center or sizable=no style attribute and run the program in the GBC, the table does expand to fill space available so it could be argued that the position=center style behaviour should be the same.
So I suspect unless I have missed something, there is not a quick answer. I would suggest you raise a support question so it can be tracked properly. Quote SUPW-655 (our internal number for the genero internal discussion) so that it can be linked to the earlier discussion from genero internal. I suspect we will need to come up with a solution that matches your example. sizable=vertical perhaps.
Reuben
