How to Use EL850DB.EXE Utility to Create PSQL Databases

Release Date: 12/4/2018

Elliott 8.5 includes features -- Report Desk for example -- that require PSQL relational data access. In the past, PSQL databases were created manually by users.  To make it easy to create PSQL databases, the new utility EL850DB.EXE is included in the Elliott 8.5 release, and you can find it in <ElliottRoot>\Bin85 folder where <ElliottRoot> is the root directory where you have Elliott 8.5 installed. You may also run this application from your Elliott 8.5 Control Center by logging in as "SUPERVISOR." Then click on the top left corner toolbar task "Config" (Elliott Global Configuration,) and go to the "Database" tab, where you can find the button "Create Databases."  This is a shortcut to launch EL850DB.EXE. Make sure you run EL850DB.EXE on the PSQL server and login as a Windows Admin or equivalent.

Prerequisite:
This utility is compatible with PSQL 11, 12 and 13. You must login as Windows Admin or equivalent to run EL850DB.EXE on the same machine as the Elliott Data (i.e., PSQL server.). 

Elliott Database Naming Convention:
From Elliott V7 to V8.5, we distributed different types of DDF files in the following folders to create PSQL databases:
  • <ElliottRoot>\DDF40 - for Elliott V7.x databases in data directory.  Standard database name will be ELLIOTTDATA.
  • <ElliottRoot>\Bin\DDF40 - for Elliott V8.0 - V8.2 databases in data directory. Standard database names will be ELIDATA.
  • <ElliottRoot>\Bin85\DDF40 - for Elliott V8.5 databases in data directory. Standard database name will be ELI85DATA.
  • <ElliottRoot>\Bin85\DDFROOT - for Elliott V8.5 databases in the root directory. Standard database name will be ELIROOT.
Since Elliott Business Software supports multiple companies, for data in folders like DATA_02, DATA_03...etc, the naming convention will be replacing "DATA" above with "DATA02," "DATA03,"...etc.  For example, for Company 10 where data is stored in <ElliottRoot>\DATA_10 folder, the corresponding Elliott 8.5 database name will be ELI85DATA10.

By default, if not specifically specified, Elliott 8.5 will assume the database name for each company by following the convention above. EL850DB.EXE helps you to create these standard database names in Elliott V8.2 or V8.5 format.

User Interface:
  
  1. Database Version - you can select the version of database to create. This can be either 8.5 or 8.2. 
  2. Elliott Root Folder - A read-only text field that indicates the location of the Elliott Root Folder.
  3. Elliott DDF Folder - A read-only text field that indicates the location of the DDF folder. For 8.5, this is {ElliottRootFolder}\bin85\DDF. For 8.2, this is {ElliottRootFolder}\bin\DDF.
  4. Elliott Root DDF Folder - A read-only text field that indicates the location of the DDF folder for Elliott Root database. Only applicable for 8.5 database.
  5. Elliott Data Folder(s) - You select which data folders to create database(s) for in this control group. This section has two list views. The left "Data folders with no database" list view shows all data folders that currently do not have a corresponding database. You can check one or more item(s) to create databases for the data folders. The right "Data folders with existing database(s)" list view shows all data folders that already have a corresponding database.
  6. Check All button - Check all items in the "Data folders with no database" list view.
  7. Uncheck All button - Uncheck all items in the "Data folders with no database" list view.
  8. Create Database(s) - Create database for all checked items in the "Data folders with no database" list view.
Differences between V8.2 and V8.5 Databases
This utility lets you create both Elliott V8.5 and V8.2 databases with Elliott's standard naming convention. 
 
Elliott 8.5 databases assume all Elliott document numbers (e.g., Invoice Number, Order Number, Purchase Order Number, Voucher Number...etc.) are in string format where you can store alphabetic values.  On the other hand, Elliott 8.2 databases assume all document numbers are numeric.

Even though you may be using Elliott 8.5 programs, you may continue to run Elliott databases in Elliott 8.2 format as long as you don't store alphabetic values in your Elliott document number fields.  You may do so because: (1) You like to evaluate Elliott 8.5 first while most of your users are running on Elliott 8.2; (2) It may take you time to convert third party applications like Crystal Reports or web applications that depend on the V8.2 web services to convert to Elliott 8.5 format.

Once you are ready, you can use the <ElliottRoot>\Bint85\DDF2BTR.EXE utility to convert your V8.2 databases to V8.5 format. After that, you are ready to store alphabetic values in your document numbers, and you can't use Elliott 8.2 and other third party applications that utilize the Elliott 8.2 format anymore. Please refer to Elliott 8.5 Release Notes and other KB articles on how to use DDF2BTR.EXE for this purpose.

Elliott 8.5 Report Desk uses the PSQL relational database to access Elliott data. It can work with either Elliott 8.2 or 8.5 database format. It is important that the corresponding databases are created on a PSQL server for Report Desk purposes.  Also, in Elliott Global Configuration, you must associate each Elliott company with the right database name. See sample screen below:

Additional Information
For information on how to create databases manually via Pervasive Control Center (PCC), please visit this knowledge base article.

Known Issue with DDF Files in DATA Folder
By design, your Elliott DDF files should reside in <ElliottRoot>\Bin\DDF40 or <ElliottRoot>\Bin85\DDF40 folders.  Then when you choose to create the corresponding Elliott database, you will specify as in the following example:
  • Dictionary: <ElliottRoot>\Bin85\DDF40
  • Data: <ElliottRoot>\DATA


We have seen that if you also have a copy of DDF files residing in the <ElliottRoot>\DATA folder, then those DDF files will override the DDF files in <ElliottRoot>\Bin85\DDF40 in the  above example.  This can cause a big problem for Elliott V8.5 when accessing data through the relational engine.  Therefore, you should not place DDF files in your DATA folder.


VYC

Elliott Version 8.5

  1. V8.5 Alpha Document Number Support
  2. Crystal Report Conversion for V8.5
  3. Animating COBOL Code in Elliott V8.5
  4. The Run Local or Hybrid Feature in Elliott 8.5
  5. How to Use EL850DB.EXE Utility to Create PSQL Databases
  6. PSQL Database Naming Convention for 8.5 Databases
  7. Showing Document Date in Links After Elliott 8.5
  8. The Lessons We Learned from Upgrading Web Service 8.2 to 8.5 in eStore
  9. Report Desk Tables
  10. Report Desk Delivery Strategy
  11. Report Desk Thresholds
  12. How Is Font Being Determined in Report Desk?
  13. How to Use DebugLogLevel Registry Value to Debug Report Desk Issues
  14. How to Use Report Desk – User Perspective
  15. How to Use Report Desk – Admin Perspective
  16. Feature - ASCII File Filter Condition in Mass Email and Export Processor
  17. How to Use Variables in Report Desk Title and Column Headings
  18. How to Override Report Desk Font and Margin Defaults
  19. Feature - List Users Acively Logged into Elliott and Optionally Send Email
  20. Feature - Allow Print One Invoice to Print Duplicate Invoices for Order Not Posted
  21. Feature - Print Range of Duplicate Unposted Orders
  22. Feature - Prevent Duplicate Invoice Numbers with Invoice Cross Reference File
  23. Feature - Last Year Net Income Layout Support
  24. Receive Message "Not Found" When Trying to Set Up Run Local
  25. Receive 'Invalid Column Name' Message After Starting to Use Alphabetic Document Numbers
  26. Feature - Invoice Log Report
  27. Feature - Add Sales or Usage to Where-Used inquiry
  28. Feature - Case Size Support for Quantity Per Box
  29. Feature - Exclude Obsolete Customers from Customer Generic Search
  30. Feature - Refresh VICS Bill of Lading
  31. Feature - Support Item Case Size in New Item CSV Import and Change Existing Item Import
  32. Feature - Copy Notes, Attributes, and Links When Copying Item Through the New Item CSV Import
  33. Feature - Enhanced Cash Receipts Processing Apply-To Range
  34. Feature - Add Links Import to System Files Setup
  35. Feature - Shipment Email Acknowledgement for Bill-To Customers
  36. Feature - Restrict Sending Tracking Number to Bill-To Customer in Shipment Email Acknowledgement
  37. Overriding Report Desk Report Configuration
  38. Report Desk: Using Global Variables and Parameters
  39. Using CheckBoxes in Report Desk
  40. Feature - Allow Source Range on Credit Card Log Report

Feedback and Knowledge Base