Elliott Database Naming Convention

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
  • EWS85DATA - V8.5 DDF for Web Services to operate on 24x7 basis which makes it difficult to update the DDF
  • ELI86DATA - V8.6 DDF
  • EWS86DATA - V8.6 DDF for Web Services to operate on 24x7 basis which makes it difficult to update the 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:
  1. ELI85DATA - based on DDF in <EllliottRoot>\Bin85\DDF40
  2. ELI85DATA02 - based on DDF in <EllliottRoot>\Bin85\DDF40
  3. ...
  4. ELI85DATA99 - based on DDF in <EllliottRoot>\Bin85\DDF40
or
  1. EWS85DATA - based on DDF in <EllliottRoot>\Bin85\DDF40\WSDDF. This for Elliott web services.  The reason we have a separate folder for web services is because it will open Elliott's DDF on 24x7 basis and make it difficult to update.  General speaking, the DDF used by web services is not required to update unless the web services is changed as well.
  2. EWS85DATA02 - based on DDF in <EllliottRoot>\Bin85\DDF40\WSDDF. Same as above.
  3. ...
  4. EWS85DATA99 - based on DDF in <EllliottRoot>\Bin85\DDF40\WSDDF.  Same as above.
Where 02 - 99 represents the company ID. ELI85DATA represents company 01. 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:
  1. ELI86DATA - based on DDF in <EllliottRoot>\Bin86\DDF40\STDDDF
  2. ELI86DATA02 - based on DDF in <EllliottRoot>\Bin86\DDF40\STDDDF
  3. ...
  4. ELI86DATA99 - based on DDF in <EllliottRoot>\Bin86\DDF40\STDDDF
or
  1. EWS86DATA - based on DDF in <EllliottRoot>\Bin86\DDF40\WSDDF.  This for Elliott web services.  The reason we have a separate folder for web services is because it will open Elliott's DDF on 24x7 basis and make it difficult to update.  General speaking, the DDF used by web services is not required to update unless the web services is changed as well.
  2. EWS86DATA02 - based on DDF in <EllliottRoot>\Bin86\DDF40\WSDDF. Same as above.
  3. ...
  4. EWS86DATA99 - based on DDF in <EllliottRoot>\Bin86\DDF40\WSDDF. Same as above.
Where 02 - 99 represents the company ID. ELI86DATA represents company 01. 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\STDDDF. 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.  

Please see the following related article for Elliott 8.6 Database Convention:

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:

JEG/EMK



    • Related Articles

    • Elliott 8.6 Database Convention & Report Desk/PowerSearch

      Release Date: 08/27/2021 Revision Date: 4/11/2022 Version: 8.6 Elliott 8.6 Database Naming Convention Elliott 8.6 now supports Report Desk and PowerSearch, features based on the PSQL relational database engine. Databases must be created for Report ...

    • A Support Case of Migrating to Different Version of DDF

      Release Date: 4/24/19 Version: All Q - I've been asked to set up UPS Worldship to access customer shipping addresses in Elliott. I've run into a problem mapping City, State, and Zip fields to Elliott. Looks like Elliott concatenates these fields to ...

    • An Example of DDF Files in DATA Folder that Can Confuse PSQL

      Release Date: 04/11/2024 Version: All Q - I tried to access Elliott Item master column ITEM_CASE_SIZE in Report Desk. In one of the Report Desk reports, I wanted to drag ITEM_CASE_SIZE to the report body. But I can't find that column under the ...

    • A Comparison of Elliott 7.5, 8.2, 8.5, 8.6 and 8.6 V2 DDF Files

      Release Date: 11/15/2022 Last Updated: 06/25/2024 Version: 7.5 & Up DDF Files are used to define the PSQL database schema. Generally speaking, we distribute five different types of DDF files for different versions of Elliott releases: 7.5 DDF: These ...

    • DDF Files in DATA Folder May Confuse PSQL

      Release Date: 04/27/2018 Q - We recently noticed a strange phenomenon where if I try to access Elliott column names in the ARCUSFIL, I find the Customer AR account is defined as CUS_AR_ACCT_NO and it is 24 digits. See sample screen below: I have an ...