*A.DBF

Wire and cable lists:

This TARGET database is used for wire lists, cable lists and cable core lists. An extended version of this database file where all connections appear twice, one in each direction, is also available. That double directed connection database is named *I.DBF.
 
The *A.DBF database is created by Dynamic OnLine with information from PDS, catalogue, numbering algorithms, symbol database etc. on request of the Report Generator.

*B.DBF

Terminal list:

This TARGET database is used for ordinary terminal lists. It also contains information about links (jumpers). An extended version of *B.DBF with support for combined terminal and cable plans following the DIN standard is also available. That TARGET database is called *X.DBF.

The *B.DBF database is created by Dynamic OnLine with information from PDS, catalogue, *J.DBF, numbering algorithms etc. on request of the Report Generator.

*C.DBF

Connection database, raw data:

This is a legacy database normally not used for reports. It was used in early versions of cadett ELSA (3.8 – 5.5) when creating external connection diagrams.

*E.DBF

Unsummarized device list:

This TARGET database has a so-called “German” format. This means that each physical device corresponds to a record in the database. This gives long lists where, for example, each single terminal occupies its own line.

Dynamic OnLine creates the database with information from PDS and the catalogue on request of the Report Generator.

*G.DBF

Base database:

Most other TARGET databases are linked to *G.DBF.

This database file is not used directly but via the other ones. Dynamic OnLine creates *G.DBF with information from PDS on request of the Report Generator.

*I.DBF

Bidirectional wire and cable core list:

This is an extended version of the *A.DBF that was introduced in cadett ELSA 7.0. This database file has the same content as *A.DBF with the difference that all connections appear twice, one in each direction.

*J.DBF

Assignments of numbering algorithms to terminal groups:

This database file is found in the SOURCE directory. It is created and maintained by the Project Module when you add or change the algorithm assignments in the project parameters, or from the terminal dialogue box in the Drawing Environment.

Strictly speaking, this is not a true TARGET database.

*L.DBF

Device list (ordering list) summarized over the entire project:

Module and wear group are considered, which makes it possible to include spare parts as well.

*R.DBF

Project bounded drawing types:

The *R.DBF has been discontinued and is not used by the current version of cadett ELSA. However, projects created by old versions of cadett ELSA may still contain this database file, and the current version is able to convert the content to the database format that is used today (DocumentCodes.dbf).

Strictly speaking, this was not a true TARGET database either.

*X.DBF

Extended terminal list following DIN standard:

The content of this database file is partly controlled by special settings in the report definitions for this special kind of report. In older versions, a configuration file called DIN.INI was used instead. The old DIN.INI is still used to specify default values for current settings. If those are missing, DIN.INI is used instead. DIN.INI is located in \ELSA\II\REPORTS.

*X.DBF is used for combined terminal and cable core lists (“terminal plans”) following DIN standard. 0X_E_EMA005 is an example of such a report definition.

*Y.DBF

Complete table of contents:

The *Y.DBF database file contains a union of *Z.DBF in the SOURCE and TARGET directories of the current project. Dynamic OnLine creates the database on request of the Report Generator. Even though this database file has a special character in many ways, it is still definitely a member of the TARGET databases.

*Z.DBF

Drawing Manager archive database:

This database file exists in double editions, one in the SOURCE directory and one in the TARGET directory. They include references to the drawing sheets and other files like PDF’s, in each directory. The Drawing Manager creates and maintains these database files, which content in principle is identical with the information that can be seen in the survey of the Drawing Manager.

Strictly speaking they are not true TARGET databases, but they can be used to create tables of contents. An even better idea is, however, to use the *Y.DBF instead.

*0.DBF

Raw connection database:

This database has been discontinued. It was used in older versions of cadett ELSA (3.8-5.5). Dynamic OnLine created the database in line with the generating process of external connection diagrams. It was never intended for report generation.

*2.DBF

Extended resources- and parts lists:

The database file is used for resource lists with amount fields (normal resource lists following IEC-standard) and parts lists sorted by placement, plant or combinations of plant and placement. Dynamic OnLine creates the database with information from PDS, catalogue etc. on request of the Report Generator.

PROJECTS.DBF

Database of project parameters:

This database file can in principle be used to create a project list. There are however several good reasons why that should not really be done.

SYMBDEF.DBF

Definitions of symbols:

This database file can in principle be used to create a list of all symbols in a symbol library. There are however strong arguments against doing so.

SYMBDEFC.DBF

Function definitions in mirror symbols:

For example, contacts in contact mirrors.