Tables / Lists(Texts)

Often position data in form of tables is returned. The individual positions usually are available as an indexed parameter group. In order to guarantee that the same text component can always be used, the indexed PG should be copied into a non-indexed PG of the same type:

f$PGKopie( ’PosList[i]’, ’part’ )

p$TDV:SMPAPI:EtTxBast( 1, ’Pos’ )

In the text component the block list data are always to be addressed using "{ DOCVARIABLE part.xxx }" .

If the individual positions of a list are returned in form of a Word table, every row in the table resembles a text component. If this text component in the table ends, Word automatically adds an additional empty line. This problem can be defused a bit if the text component at the end after the table still contains a row of size 1 pt. This row can even contain a frame line on its left or right border so that a continuous frame line at the borders is created. However, continuous internal grid lines are not possible.

When creating a document from ePOS it is simpler to use tabulators instead of tables (right or left aligned tabulators , or decimal tabulators).

Another alternative is to add a Word table directly at the end of a document using p$TDV:SMPAPI:EtTxTab and write the contents directly into the table through p$TDV:SMPAPI:EtTxTxt. A new table row is – similar to the interactive method - created through a tab symbol at the end of the last table row.

If a table is to receive column headlines on each new page it is best to insert this headline into the page header (see also remarks dealing with section breaks).