This is an internal system module / table and must not be changed.
TradeDesign does not support customization of this module / table.
This table holds the named counters and their current value.
| Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
|---|---|---|---|---|---|---|---|---|---|
| COUNAM | Name of the Counter | Text | 8 | 1 | Edit | Yes | Public | ||
| COUVAL | Counter Value | Numeric | 18 | 0 | Edit | Yes | Public | ||
| COUSTP | Update in Steps | Numeric | 18 | 0 | Edit | Yes | Public |
| Name | Fields | Properties |
|---|---|---|
| COUIDX | COUNAM | Unique |
/
COUNAM
Any counter name might be used and will automatically be created by TradeDesign as a new counter with a starting value of 1 and the default update steps. The counter used to create the INR of a table uses the ID of the table as counter name. Counters which are used to create reference numbers should use counter names, which are different from the table names. Typical names are based on the two characters long business sector code and the year the counter is valid for.
Any counter name can be used. TradeDesign then uses this to automatically create a new counter which starts at 1 and contains the default update intervals. The counter used to create the identification number (INR) of a table uses the this as the counter name. Counters used to create reference numbers should use counter names that are different from table names. Typical names are based on the two-digit business sector code and the year for which the counter is valid.
This field holds the next available counter value for the specified counter.
This field holds the next available counter value for the specified counter.
This field holds a stepping in which counters are taken from the database table. If a sequential numbering without any unused number is essential, then the stepping has to be set to 1. Any value bigger than 1 increases the performance in extracting counter values, because of less database traffic but potentially creates not used numbers, as multiple users get separate groups of numbers and if they are not fully used, the unused numbers of the group will be lost upon the end of the session.
This field contains the sequence in which counters are taken from the database table. If it is important to use sequential numbering (without drawing on unused numbers), then the increment has to be set to 1. Any value bigger than 1 increases the performance in extracting counter values, due to lower database traffic. However, this may generate non-used numbers, as multiple users receive separate groups of numbers. If these numbers are not fully used, unused numbers will be lost at the end of the session.