Elliott Database Naming Convention

Release Date: 06/30/20
Version: 7.x & Up

Listed below are examples of standard Elliott database naming conventions for current and future versions of Elliott:
  • ELLIOTTDATA           V7.X DDF
  • ELIDATA                    V8.0-8.2 DDF
  • ELI85DATA                V8.5 DDF
  • ELI86DATA                V8.6 DDF
  • ELI86ROOT               V8.6 DDF for <ElliottRoot> directory data
The DATA represent Elliott data in company 1.  For other companies, we add two digits (a numeric number like 99) at the end.  For example:

For Elliott 7.x, we typically name the database as follows:
ELLIOTTDATA
ELLIOTTDATA02
...
ELLIOTTDATA99
Where 02 - 99 represents the company ID. ELLIOTTDATA represents company 01. The DDF is based on the folder <ElliottRoot>\DDF40.

For Elliott 8.0 - 8.2, we typically name the database as follows:
ELIDATA
ELIDATA02
...
ELIDATA99
Where 02 - 99 represents the company ID. ELIDATA represents company 01. The DDF is based on the folder <ElliottRoot>\Bin\DDF40.

For Elliott 8.5, we typically name the database as follows:
ELI85DATA
ELI85DATA02
...
ELI85DATA99
Where 02 - 99 represents the company ID. ELI85DATA represents company 01. The DDF is based on the folder <ElliottRoot>\Bin85\DDF40. The main change in Elliott 8.5 DDFs from prior versions is that all Elliott document numbers are assumed to be in string format where alphabetic values can be stored.  Additionally, we now have added various NSCTLFIL_9999 table definitions so you can access each NSCTLFIL record with proper column definitions. Even if you are using Elliott 8.5 but did not convert your database to alphabetic document format, then you should continue to use the Elliott 8.0 - 8.2 DDF databases (i.e., ELIDATA.)

For Elliott 8.6, we typically name the database as follows:
ELI86DATA
ELI86DATA02
...
ELI86DATA99
Where 02 - 99 represents the company ID. ELI86DATA represents company 01. The DDF is based on the folder <ElliottRoot>\Bin86\DDF40.  Like Elliott 8.5, Elliott 8.6 DDF assumes all document numbers are stored in string format. Even if you are using Elliott 8.6 but did not convert your database to alphabetic document format, then you should continue to use the Elliott 8.0 - 8.2 DDF databases (i.e., ELIDATA.)

The following sample screen shows how ELI86DATA03 is defined in the database properties of PSQL Control Center:


Note that we use the local path on the  PSQL server to define the location of <ElliottRoot>.  For example, if your <ElliottRoot> normally refers to M:\Elliott7, then in our example above the corresponding local path is D:\Acct\Elliott7.

Elliott 8.6 also requires a special database name:
ELI86ROOT
Where the DDF is based on the folder <ElliottRoot>\Bin86\DDFROOT. This database contains the database layout for *.BTR file <ElliottRoot>. Typically, these are Report Desk data where the report definition applies to all companies. See the following sample screen for how ELI86ROOT is defined in database properties:


If you follow the above recommended default naming convention, it will make the setup of Report Desk easier, but you don't have to -- especially if you have a customized DDF.  

Beginning with Elliott V8.6, it is necessary to associate the database names in PSQL Control Center to the company data directories in order to support the Report Desk feature.  

Create Elliott Databases by Using EL850DB.EXE or EL860DB.EXE Utility

You can create Elliott 8.5 or 8.6 databases with the standard naming convention by using the EL850DB.EXE or EL860DB.EXE utility. Please refer to the following KB article for more detail:

Feedback and Knowledge Base