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 the Ship-To Address 3 field. Worldship is unable to digest this.

What do you recommend?

A - You must be using a very old copy of DDF. As far as I know, Elliott DDF in 7.5, 8.x and above all have Order Ship to City, State and Zip fields separated with filler in between. Please download the latest Elliott version. By default, the Elliott installation Package does not override the existing DDF, so you need to use a custom installation to override the existing DDF. You may want to backup your existing DDF before you do that. One of the reasons we don’t install DDF when updating Elliott is because DDF is constantly open by users or the PSQL server. So you need to make sure no process is opening the DDF files before you try to install the new version. Elliott’s DDF is in either <ElliottRoot>\DDF40 or <ElliottRoot>\Bin\DDF40 depending on which Elliott version you are running. You can find out if any process is opening DDF files through the PSQL monitor utility.

Q - I found out we have DDFs all over. I’m assuming the DDFs in use are the ones specified in the PSQL database properties, right?

We are running EL800 and EL800P only, so my focus should be on <ElliottRoot>\Bin\DDF40 only, right? Looks like I’ll need to update the Dictionary Location. I also notice the mapped Data Directory drives need the path updated to point to the data directory. 

There are at least 4 DDF directories in their installation besides the default locations you describe. Can I remove these as long as the Dictionary Location setting is set to <ElliottRoot>\Bin\DDF40 for all databases?

Any chance of things blowing up once the correct DDF files are in place?

AOur typical naming conventions for the database are:
                ELLIOTTDATA for V7.5 DDF         which point to <ElliottRoot>\DDF40 folder
                ELIDATA for V8.0 DDF                   which point to <ElliottRoot>\Bin\DDF40 folder
I can understand your concern that things may blow up if you keep the same database name and change the folder under the database properties.

I am not sure about the database name you use. Let’s assume you are using ELLIOTTDATA and point to an old DDF folder. To mitigate that risk, your best bet is to create a database name like ELIDATA that points to the  <ElliottRoot>\Bin\DDF40 folder. Then migrate your application from using ELLIOTTDATA to use ELIDATA. If everything still works, great! If something blows up, then change it back to ELLIOTTDATA and take your time to investigate why it blew up and address it accordingly before using the new database name again.

The biggest changes of 8.0 DDF are the following:
  1. The GL account consists of three parts: Main, Profit Center and Department. The 7.5 DDF was defined inconsistently in this area. Sometimes it defines a GL account with three fields. Sometimes it defines the whole GL account as one field. In V8.0 DDF, we consistently define the whole GL account as one field.
  2. Some of the tables have columns like FILLER*. They are all now changed to TABLENAME_FILLER* where TABLENAME is the 8-digit table name. This is an effort to make sure there is not the same column name among different tables.
Whether these changes will affect your existing third party applications (i.e., Crystal Reports, Excel Query, Manifest System..etc.) or not is hard to say.  Therefore, adopting the previously suggested steps to create the new database name that points to the new DDF files is a safer way to go.  Once you have everyone migrated to the new database without issue, you can then disable the old database. You can do so by changing the database properties to point to an invalid location for the DDF files. If someone complains their application is no longer working without errors, then you know they are still using the old database name. This ensures all users migrate to the new database name.

Please also read the following related KB article:
 

EMK

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
  41. What Does Btrieve Error 080 Mean?

Feedback and Knowledge Base