A layout element called a table is a rectangular array in cells of which data values are located. The cell values can belong to any types of ObjectLand table data with the exception of OLE objects.
The term “table” has been widely used in previous sections of the documentation as a name of one of the main components of GDB and EDB. In the present chapter this term denotes a completely different thing, namely: one of layout elements. There is some connection between two meanings of the word “table”. The main purpose of a table as a layout element is displaying data present in GDB queries, and the queries, in their turn, are users' representations of data from tables – GDB components. Connections and differences between these three terms can be shortly formulated like this:
A table as GDB component serves for storing data organized as a set of records and fields.
A query is built on the basis of one or several tables, it determines what records and fields and also what values calculated on the basis of table data should be included into user representation.
A table as a layout element provides display of the rectangular array of data on a layout page. Such parameters as the total size of a table, sizes of individual cells, format of displaying numbers and other data in cells, font, background color and other displaying parameters are specified for a table. Table cells can be linked with field values of query records, but can also contain values not linked with any query (for example, column captions).
While GDB components, tables and queries, can have practically unlimited number of records and fields, the number of rows and columns of a table in a layout is naturally limited by the necessity to fit the table into a layout page.
 |  |
