PSQL Database Naming Convention for 8.5 Databases

Elliott Database Naming Convention


Listed below is the 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
  • ELI90DATA                V9.0 & after DDF

Standards for V8.5

Beginning with Elliott V8.5, it is necessary to associate the database names in PSQL Control Center to the Company data directories.  They will default as follows:

  • ELIROOT               for tables in the root directory, this is needed for the new report writer in 8.3.
  • DDF: <ElliottRoot>\Bin85\DDFROOT
  • Data: <ElliottRoot>
  • ELI85DATA             for Company 01 tables
  • DDF: <ElliottRoot>\Bin85\DDF40
  • Data: <ElliottRoot>\Data
  • ELI85DATA02         for Company 02 tables
  • ELI85DATA03         for Company 03 tables
  • etc.

These are the defaults.  However, if your database is customized, a separate set of DDF and database names are created.  Then you need to override the standard naming assumption by Elliott in EL850.CFG file. For example, you may add a section as follows:

  • [Database]:
  • Server=TS4
  • Root=XXXROOT
  • Company01-DSN=XXX85DATA
  • Company02-DSN=XXX85DATA02
  • etc.

The Server entry is required for using new Report Writer.  It is used to construct the connection strings to the databases.

The Root and CompanyNN-DSN entries do not have to be present in EL850.CFG.  When they are not present, the default database names (ELIROOT and ELI85DATA ...etc.) are assumed.

The main change in Elliott 8.5 DDFs is that all Elliott document numbers are assumed to be in String format where alphabetic values can be stored.  In addition, we added the ELIROOT convention to support the root directory database files in order for the new Report Desk to function.  Additionally, we now have added various NSCTLFIL_9999 table definition so you can access each NSCTLFIL record with proper column definitions.

Create Elliott 8.5 Databases by Using EL850DB.EXE Utility

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

Elliott Version 8.5

  1. V8.5 Alpha Document Number Support
  2. Crystal Report Conversion for V8.5
  3. The Run Local or Hybrid Feature in Elliott 8.5
  4. How to Use EL850DB.EXE Utility to Create PSQL Databases
  5. PSQL Database Naming Convention for 8.5 Databases
  6. Showing Document Date in Links After Elliott 8.5
  7. The Lessons We Learned from Upgrading Web Service 8.2 to 8.5 in eStore
  8. Report Desk Tables
  9. Report Desk Delivery Strategy
  10. Report Desk Thresholds
  11. How Is Font Being Determined in Report Desk?
  12. How to Use DebugLogLevel Registry Value to Debug Report Desk Issues
  13. How to Use Report Desk – User Perspective
  14. How to Use Report Desk – Admin Perspective
  15. Feature - ASCII File Filter Condition in Mass Email and Export Processor
  16. How to Use Variables in Report Desk Title and Column Headings
  17. How to Override Report Desk Font and Margin Defaults
  18. Feature - List Users Acively Logged into Elliott and Optionally Send Email
  19. Feature - Allow Print One Invoice to Print Duplicate Invoices for Order Not Posted
  20. Feature - Print Range of Duplicate Unposted Orders
  21. Feature - Prevent Duplicate Invoice Numbers with Invoice Cross Reference File
  22. Feature - Last Year Net Income Layout Support
  23. Receive Message "Not Found" When Trying to Set Up Run Local
  24. Receive 'Invalid Column Name' Message After Starting to Use Alphabetic Document Numbers
  25. Feature - Invoice Log Report
  26. Feature - Add Sales or Usage to Where-Used inquiry
  27. Feature - Case Size Support for Quantity Per Box
  28. Feature - Exclude Obsolete Customers from Customer Generic Search
  29. Feature - Refresh VICS Bill of Lading
  30. Feature - Support Item Case Size in New Item CSV Import and Change Existing Item Import
  31. Feature - Copy Notes, Attributes, and Links When Copying Item Through the New Item CSV Import
  32. Feature - Enhanced Cash Receipts Processing Apply-To Range
  33. Feature - Add Links Import to System Files Setup
  34. Feature - Shipment Email Acknowledgement for Bill-To Customers
  35. Feature - Restrict Sending Tracking Number to Bill-To Customer in Shipment Email Acknowledgement
  36. Overriding Report Desk Report Configuration
  37. Report Desk: Using Global Variables and Parameters
  38. Using CheckBoxes in Report Desk
  39. Feature - Allow Source Range on Credit Card Log Report
  40. Feature - Indented Bill of Material CSV
  41. Feature - Stock Status Reports Add Include with Alloc or On Order Quantity Option
  42. Feature - Release Manually Held Orders
  43. Report Desk: Optional File Input Parameter
  44. Feature - Create Shipment Records When Complete Bill Of Lading
  45. Feature - Print Warning Msg for Cancelled PO Line Item
  46. Feature - Export 25-Character PO Number in Expanded Aging Report CSV File
  47. Feature - Show Pending Cash Receipts in Payment History Inquiry
  48. Feature - Show Customer Note Fields in Payment History Inquiry
  49. Receive "Error Getting List of Override Reports" When Printing Report
  50. Feature - Fields Added to User-Defined CSV to Support EDI 846
  51. Feature - Credit Memo Warning When Fully Paid
  52. Feature - Create Shipment Verification Box Records Through Billing CSV Interface
  53. Feature - Show Box ID on Order Inquiry Shipment Data Screen
  54. Feature - Print Error Message If Inventory Transaction Distributions Are Missing
  55. Feature - Customer CSV Import
  56. Feature - Alleviate Error 25 When Two Users Import Sales Orders Simultaneously
  57. Feature - Use Note Type for Special Instructions on VICS BOL
  58. Feature - VICS BOL to Enforce Shipment Verification Before Printing of BOL
  59. Feature - Order/Invoice Inquiry Box Serial Number Drill Down
  60. Feature - Delete Order Tracking Note When Void Completed VICS BOL
  61. Feature - Picking Ticket For Customer 2 Event

Feedback and Knowledge Base