Elliott Database Naming Convention

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

Listed below are example of standard Elliott database naming convention 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 numeric number like 99 behind.  For examples,

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 version 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 definition so you can access each NSCTLFIL record with proper column definitions. Even if you are using Elliott 8.5, but if you 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 if you 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 for how ELI86DATA03 is defined in 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 refer to M:\Elliott7, then it 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 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 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:

Pervasive PSQL

  1. Btrieve Error Codes 001 - 199
  2. Btrieve Error Codes 3000 - 3099
  3. Btrieve Error Codes 3100 - 3199
  4. PSQL Version Required by Each Elliott Version
  5. Do I Need to Change PSQL Server Engine Default Parameters After Installing It?
  6. New Elliott PSQL Server Processor and RAM Suggestions
  7. Can I Dynamically Adjust Elliott / PSQL 11 Server Memory?
  8. Received "Your Computer Does Not Have PSQL 10 or 11 Client " Even though PSQL Client Is Just Installed
  9. Btrieve Error 161 on Password File When Starting Up Elliott
  10. Problems with Using Pervasive Rebuild Utility on APOPNFIL and AROPNFIL Tables
  11. Security Issue with Installing PSQL Client Remotely on User's Workstation
  12. PSQL and Distributed File System (DFS)
  13. How Do I Turn on PSQL Relational Engine Security?
  14. An Example of Debugging NOTE_ORD_VIEW PSQL Expression Evaluation Error
  15. Btrieve Error 025 on COP Open Order by Salesman Report
  16. What Is the *.^01 File for My PSQL Btrieve Table?
  17. Suggested Files to be Monitored by Audit Master
  18. Pervasive Backup Agent Is Not Compatible with Creating Work Files
  19. Hardware Recommendations for Your PSQL Database Server
  20. How to Optimize SQL SELECT Statement When Retrieving Data from Invoice History
  21. New User-Defined Functions in Elliott DDF
  22. How to Improve Query Performance When Retrieving Data from Notes & Invoice History
  23. How to Retrieve Tracking Number for an Order from Notes
  24. Actian PSQL Not Started Automatically After Server Reboot
  25. Create a New Database in the PCC for Relational Engine Access
  26. Slow PSQL Relational Engine Performance
  27. IPV6 May Cause Problem for PSQL 11 Relational Query
  28. DDF Files in DATA Folder May Confuse PSQL
  29. What to Do When PSQL 11 License Is Disabled
  30. Quick Installation Guide for Audit Master
  31. Quick User Guide for Audit Master
  32. PSQL 13, Micrsoft SQL Integration Service & Pervasive PSQL OLE DB Provider
  33. Your Firewall Needs to Allow Outbound Traffic to the Netherlands for PSQL Licensing Server Purposes
  34. A Case of Btrieve Error 046 on ARCRCLOG A/R Credit Card Log File
  35. A Support Case of Migrating to Different Version of DDF
  36. How to Clear the Message "Unable to Read your Users record (9/068)"
  37. Setup of the PSQL 13 Report Engine
  38. How to Create CPHSTTRX_VIEW with Left Join to CPINVHDR Due to Invoice Database Archive
  39. How to Access Elliott's Data by Using Query in Microsoft Office Excel 2019
  40. Elliott Database Naming Convention

Feedback and Knowledge Base