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 are the DDF files that reside in the <ElliottRoot>\DDF40 folder. We no longer distribute these DDF files.
- 8.2 DDF: These are the DDF files that reside in the <ElliottRoot>\Bin\DDF40 folder. Generally speaking, they are identical to 8.6 DDF files except the document number fields are defined as numeric. All string fields are case insensitive except that the index columns are defined as case sensitive. There may be some minor issues with PowerSearch related to case sensitivity. Our primary intention with this DDF is if you have not converted your database for alphabetic document numbers, then you can use this DDF and it does not require database conversion for a legacy DB to use it. The naming convention is ELIDATA*.
- 8.5 DDF: These are the DDF files that reside in the <ElliottRoot>\Bin85\DDF40 folder. They are identical to 8.6 DDF files except all string key fields are case insensitive. The naming convention is ELI85DATA*. These DDF files are provided for backward compatibility with those users who have converted to the 8.5 DB. Before these users convert to using the 8.6 DB, they can use the 8.5 DDF in the interim.
- 8.6 DDF: These are the DDF files that reside in the <ElliottRoot>\Bin86\DDF40 and <ElliottRoot>\Bin86\DDFROOT folders. Generally speaking, the DDF files in the <ElliottRoot>\Bin86\DDF40 folder are identical to 8.5 DDF files. The index columns are defined as case sensitive except that name, description, and email addresses are defined as case insensitive. Like 8.2 and 8.5, all non-index string columns are defined as case insensitive to facilitate searching. We discovered there are some disadvantages in making string key fields case insensitive as in 8.5 DDF and hence reversed course with 8.6 DDF files. The naming convention is ELI86DATA*. The DDF files in the <ElliottRoot>\Bin86\DDFROOT folder will be used to create database ELI86ROOT which contains the definition of BTR files in the <ElliottRoot> folder. In Elliott 8.6, features like Report Desk, PowerSearch, and Avalara rely on BTR files in the <ElliottRoot> folder, which relies on DDF files in <ElliottRoot>\Bin86\DDFROOT to access. To use 8.6 DDF, you are required to go through DB conversion. Before you can do that, you can still use the DDF for 7.5, 8.2, and 8.5. We recommend all users migrate to 8.6 DDF eventually.
- 8.6 V2 DDF: These are the DDF files that reside in the <ElliottRoot>\Bin86\DDFV2. They are similar to the 8.6 DDF. The naming convention is ELI86DATA*V2. This DDF is created based on the PSQL DDF Schema 2, which allows longer column names. As a result, we have expanded the column names up to 30 characters and made them more user-friendly. It is expected that this set of DDFs will be used for the development of future Elliott solutions. To use the 8.6 V2 DDF, you are required to go through a DB conversion. Before you do that, you can still use the DDF for versions 7.5, 8.2, and 8.5. The 8.6 V2 DDF can be used side by side with the 8.6 DDF. We recommend that all users eventually migrate to the 8.6 and 8.6 V2 DDF.
We no longer distribute 7.5 DDF files. On the other hand, we continue to distribute 8.2, 8.5, and 8.6 DDF files. During an Elliott 8.5 installation, the system will install updated 8.2 and 8.5 DDF files. During an Elliott 8.6 installation, the system will install updated 8.2 and 8.5 DDF files. We no longer distribute 8.2 updates. But we do distribute 8.2 updated DDF files.
After Elliott 8.6 installation, we require that the admin user login to Elliott 8.6 as SUPERVISOR to synchronize DDF files for 8.2 and 8.6. Please see the following KB article for more details:
The following is a summary comparison of these DDF files:
| |
7.5 |
8.2 |
8.5 |
8.6 |
8.6 V2 |
| Subfolder |
.\DDF40 |
.\Bin\DDF40 |
.\Bin85\DDF40 |
.\Bin86\DDF40 |
.\Bin86\DDFV2 |
| DB
Naming Convention |
ELLIOTTDATA* |
ELIDATA* |
ELI85DATA* |
ELI85DATA*
ELI86ROOT |
ELI85DATA*V2
ELI86ROOT |
| Document No. |
Numeric |
Numeric |
String |
String |
String |
| Non-Index Field |
Case Insensitive |
Case Insensitive |
Case Insensitive |
Case Insensitive |
Case Insensitive |
| All Index Fields Except Name, Description
& Emails Address |
Case Sensitive |
Case Sensitive |
Case Insensitive |
Case Sensitive |
Case Sensitive |
| Index Fields of Name, Description &
Emails Address |
Case Sensitive |
Case Sensitive |
Case Insensitive |
Case Insensitive |
Case Insensitive |
| PO number fields (25 character field) |
Case Sensitive |
Case Sensitive |
Case Sensitive |
Case Sensitive |
Case Sensitive |
| Support Status |
Not Supported |
Supported |
Supported |
Supported |
Supported |
| To be Used When |
To be compatible with Old Web Services or 3rd
party application. Use Numeric Doc# & DB has not been converted |
Use Numeric Doc# |
Use String Doc# & DB converted to 8.5 format |
Use String Doc# & DB converted to 8.6 format |
Use String Doc# & DB converted to 8.6 format
– Used with future Elliott solutions. |
|
| Avalara Interface |
Not Compatible |
Not Compatible |
Compatible |
Compatible |
Not Compatible |
| Report Desk |
Compatible |
Compatible |
Compatible |
Compatible |
Not Compatible |
| Power Search |
Compatible (see known issue) |
Compatible (see known issue) |
Compatible |
Compatible |
Not Compatible |
|
| Known Issue |
The searching of name,
description & email address are case sensitive |
The searching of name, description
& email address are case sensitive |
May result in strange behavior
when primary key value has lower case values or special characters |
None |
None |
| DB Conversion Required |
No |
No |
8.5 DB conversion Required |
8.6 DB Conversion Required |
8.6 DB Conversion Required |
DDF Installation Comparison
This section compares the difference between V8.5 and V8.6 DDF Installation. The main issue is if you are using the PSQL (Actian Zan) on a 24x7 basis, then we can't update the DDF files being used. Therefore, the strategy is to update the DDF files in the LASTUPDATE subfolder which we don't expect any third party application to use. You need to either manually copy the DDF files in LASTUPDATE folder to the final folder, or you can login as Elliott SUPERVISOR which will attempt to copy on your behalf.
Elliott 8.5 Installation
Elliott 8.5 installation utility will install Elliott 8.5 and 8.2 DDF into the following folders:
- <ElliottRoot>\Bin85\DDF40: The DDF files in this folder are being referenced by Elliott V8.5 upon startup. Elliott will read the DDF files, cache them in the memory and close the DDF files. Our 8.5 convention is also to create a PSQL (Actian Zen) database by using DDF files in this folder. However, this can create installation conflict. Therefore, our Elliott 8.5 installation utility does not update DDF files in this folder. Instead, we install them in the <ElliottRoot>\Bin85\DDF40\LASTUPDATE folder. See below explanation for more details.
- <ElliottRoot>\Bin85\DDF40\LASTUPDATE: We do not expect any application to reference DDF files in this folder. Therefore, there should not be any Elliott 8.5 installation conflict. After the installation of Elliott 8.5, if you have any third-party applications like websites or Crystal Reports, you should manually copy the DDF files in this folder to the destination like <ElliottRoot>\Bin85\DDF40 or <ElliottRoot>\Bin85\DDF40\STDDDF. If the target DDF files are used on a 24x7 basis, you many need to shut down the PSQL (Actian Zen) engine in order to update them.
- <ElliottRoot>\Bin\DDF40\LASTUPDATE: This is the DDF file for Elliott 8.2. Even though the name implies this is for Elliott 8.2, in reality this DDF is for any Elliott users who are still using the document number in numeric format, regardless of what Elliott version you are using. The DDF files in this folder have the document number field defined as numeric. This includes order number, invoice number, voucher number …etc. If you never converted your database document number to alphabetic format, then you should use this set of DDFs. Chances are your PSQL (Actian Zen) database is using DDF files in <ElliottRoot>\Bin\DDF40\ or <ElliottRoot>\Bin\DDF40\STDDDF folders. So you need to manually copy the DDF files in LASTUPDATE folder accordingly. If you have a website or other third-party tools and reference those DDF files on 24x7 basis, you many need to shut down the PSQL (Actian Zen) engine in order to update them.
Elliott 8.6 Installation
Elliott 8.6 installation utility will install Elliott 8.6 and 8.2 DDF into the following folders:
- <ElliottRoot>\Bin86\DDF40: The DDF files in this folder are being referenced by Elliott V8.6 upon startup. Elliott will read the DDF files, cache them in the memory and close the DDF files. Hence, we do not expect any installation conflict so the 8.6 installation will update DDF files in this folder. Keep in mind, unlike Elliott 8.5, our 8.6 convention is to create a PSQL (Actian Zen) database by using DDF files in the <ElliottRoot>\Bin86\DDF40\STDDDF folder.
- <ElliottRoot>\Bin86\DDF40\LASTUPDATE: We do not expect any application to reference DDF files in this folder. Therefore, there should not be any Elliott 8.6 installation conflict. After the installation of Elliott 8.6, if you have any third-party applications like websites or Crystal Reports, you can manually copy the DDF files in this folder to the destination like <ElliottRoot>\Bin86\DDF40\STDDDF. Alternatively, you can login as SUPERVISOR in Elliott 8.6, and the system will automatically copy the DDF files for you if there's no conflict. If the target DDF files are used on a 24x7 basis, you many need to stop and restart the PSQL (Actian Zen) engine in order to update them.
- <ElliottRoot>\Bin\DDF40\LASTUPDATE: This the DDF file for Elliott 8.2. Even though the name implies this is for Elliott 8.2, in reality, this DDF is for any Elliott users who are still using the document numbers in numeric format, regardless of what Elliott version you are using. The DDF files in this folder have the document number field defined as numeric. This includes order number, invoice number, voucher number …etc. If you never converted your database document numbers to alphabetic format, then you should use this set of DDFs. Chances are your PSQL (Actian Zen) database is using DDF files in the <ElliottRoot>\Bin\DDF40\ or <ElliottRoot>\Bin\DDF40\STDDDF folders. So you need to manually copy the DDF files in LASTUPDATE folder accordingly. If you have a website or other third-party tools and reference those DDF files on 24x7 basis, you many need to shut down the PSQL (Actian Zen) engine in order to update them.
EMK