BOI Software Entwicklung und Vertrieb GmbH

Phone: +43 (0) 732 / 736423 - 0

Spazgasse 4


4040 Linz, Austria

Enhanced Table Definitions

The Enhanced Table Definitions allow extended work with tables with highest usability. TABEX/4 Enhanced Table Definitions comprise:

  1. Consistency and Plausibility Checks
  2. RI allocation (Referential Integrity Checks)
  3. Table Views
  4. Use of Table Names from Relational Databases for Management for RDB Tables
  5. Table-specific Help
  6. Data Model Driven Table Management within a workflow

1. Consistency and Plausibility Checks

Check rules for data can be defined in the form of so called check tables. By means of these check tables the input of data can be constrained to special values or a range of values for example.

Logical operators and conditional execution allow the realisation of complex check rules.

An exit interface enables the embedding of program logic.

2. RI allocation (Referential Integrity Checks)

If tables are joined by a RI allocation, referential integrity is checked during table management.

3. Table Views

By using a SELECT statement, TABEX/4 table data can be retrieved or saved as views or new tables. The syntax corresponds to the SQL-standard and has some TABEX specific enhancements.

The aim of this VIEW option is to provide the data in a form, that allows optimal access and optimal display, e.g. for the print output.

4. Use of Table Names from Relational Databases for Management for RDB Tables

RDB-Table Names are usually allocated to shorter TABEX/4 table names in order to execute check table, RI-allocations, TABEX/4 authorizations or other functionalities which are related via TABEX/4 names.

This option offers the possibility to use longer, but established RDB table names for all TABEX/4 functions for display and maintenance of RDB-Tables so that users can work with their tables in the usual manner.

5. Table-specific Help

In order to optimally support users, help texts for tables can be maintained in a TABEX/4 table. A help text can, for instance, define the range of values for a table field. 

The objective is to enable end users to work with TABEX/4 independently and without the need for special training or complex documentation.

6. Data Model Driven Table Management within a Workflow

It is possible to define how tables are allocated in a theoretical data model (parent-child rules).

Changes in one table can necessitate changes in related tables.
TABEX/4’s Data-Model Driven Table Management makes it possible to execute changes of several related tables in one workflow, taking into account check rules and carrying out logging.

It is possible to interrupt a workflow e.g. during night hours.


Changes in ESA data spaces, efficient migration and a new success story: Learn more in our newsletter!


Migration Packages

BOI GmbH offers migration packages for the table management systems SPITAB, TABSYS and VTAS.


» Migration Packages

Success Stories

GDIS and BOI: Carrying on the Success

With TABEX4 JTC, GDIS has introduced the world's fastest Java interface for table access on customer and control data. Learn the details in our new Success Story.


» read this Success Story

» read more Success Stories