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

   In addition to the management of traditional files, Table files can be
   defined. The features of this kind of file is that all the records of all
   the files defined as tables, are stored inside a single system file
   (dBTabD.dbf).

   The system will only use 2 file handles for accessing all the table
   files, namely one for the file itself and one for the associated index.
   This also allows for a lower memory overhead.

   This kind of file is useful when a group of articulate files containing a
   limited number of fields and/or records that are rarely modified, is to be
   managed (ex. tax table, payment codes, agent numbers, etc.).
    To define a table file it is sufficient, in the file definition frame
   (Dictionary environment), to set the file type to "dBsee Table".

   The advantages coming from a table file are multiple.

   Managing a Table file is completely automated, refering to the search
   window, the acquisition, uniqueness checks, modification of inserted
   values and management of the indexes.

   The system can also prevent form modifying the Table file's data. This
   setting can for example be used to allow access only by the program
   administrator. The inhibition for users from changing the data is done in
   the dbStart.INI configuration module present in the EXE sub-directory
   of the current project, activating/deactivating data entry on the tables
   by entering YES or NO in the TabModify parameter.