Click above to get retro games delivered to your door ever month!

   In order to optimise the application's performance, table files can be
   defined. All the data (records) of the files defined as tables are saved
   in a single file (dBTabD.dbf). This file groups the information contained
   in each of the tables. The application uses only two file handles for ALL
   the table files (DBF and NTX). This makes it possible to have a smaller
   overhead of memory.

   The management of table files (data entry, search windows and reports), is
   completely automated by library modules; no additional source code needs
   to be generated. This notably decreases the time necessary to complete the
   application, and also allows to reduce the size of the program.

   It is suggested to use a table file for the management of secondary files
   that contain little information (eventually codified) like payment
   types (Code and Description) or Table of categories that don't need
   special controls. Tables are also managed as "terminal" files (they are
   the end of a relational branch).

   Concentrating all the data in a single file can also determine slower
   response times. It is, therefore, better to use this type only for files
   that will contain a limited number of fields and/or records (tax chart,
   agent table, etc.).