Kbase 19006: Loading a Version 9.x .df file into Version 8.x
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
18/05/2006 |
|
SUMMARY:
This solution applies to Progress Database/Dictionary Versions 9.x and 8.x. You might need to load a schema generated in Version 9.x into a Version 8.x database. The Version 9.x .df file differs slightly from the .df in Version 8.x and because of this, the load does not work correctly.
This Knowledge Base solution discusses how to work around the problem.
EXPLANATION:
Three of the new features that are introduced in the Version 9.0 database have changed the structure of the .df file and therefore stop the loading into Version 8.x. They are:
- AREA "<areaname>"
This indicates which storage area a table or index belongs
to. It appears in the ADD TABLE or ADD INDEX statement in
the .df file.
- POSITION <position>
This indicates the position of this field within the table.
It was added make it easier to work with Cycle Redundancy
Checks (CRC). POSITION appears in each ADD FIELD statement.
- SQL-WIDTH <width value>
This line is added to the .df file beginning with Version
9.0B. It is a requirement for the SQL-92 engine.
SOLUTION:
To allow the Version 9.0 .df file to be loaded in the Version 8.x Data Dictionary, remove the AREA, POSITION, and SQL-WIDTH lines from the .df file with a text editor.
A second possible workaround is:
If Version 8.x is installed, you can recompile the Version 8.x
dictionary dump routines in the Version 9.x client and put them
higher in the PROPATH than the Version 9.x libraries. This
solution has not been fully tested and is not supported by
Progress Software.
Reference to Written Documentation:
Progress Knowledge Base Solutions:
20013, "How to Load a V8 Schema (.df file) in a V9 Database"
21762, "How To Convert Database Schema File (.df) from V9 to V8"