TableGrid best practices and advice?

rbuser

Hello,

At last, I have RB 16.02 in XE7. I am now beginning to create a base
report form, and some subreports which I hope will give me what I need
to substantially reduce the hand coded content in many of our legacy
reports.

My question right now is with respect to a fairly general application
of the TableGrid. In many cases, I need a grid which has one or two
rows of header content (column captions.) The vody of the grid will
contain DBText objects which are populated dynamically. So what I
wonder is this: Will it be best to put these grids into subreports,
such that I can place the headers into the header band of the
subreport, and the content into the detail band? And therefore,
prsumably, if totals or a summary are needed, they would be in the
footer band?

Sorry for the generality of this question, but as I am just about to
begin using the TableGrid, I am hoping to design any mis-steps.

Thanks,

Bill

nicocizik

Hi Bill,

The TableGrid component is designed to be a stand-alone grid that
remains inside a single band. It may be possible to create multiple
TableGrids that span bands, however this is not something we necessarily
intended when creating the component.

What you are describing is a basic report design (Header - Detail (data)
- Footer/Summary). The TableGrid is not required for this basic design
but it may make enclosing each value with lines or shapes somewhat easier.

Ultimately the best way to become accustomed to each component in
ReportBuilder is to try multiple designs and layouts to find the one
that meets your needs.