Kbase P14815: Object type records seem to have been corrupted during the upgrade.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/01/2005 |
|
Status: Unverified
FACT(s) (Environment):
Roundtable 9.x
Dynamics 2.0A
SYMPTOM(s):
Object type records seem to have been corrupted during the upgrade.
CAUSE:
BUG# 20021128-009 WONTFIX. Not only related to RTB.
CAUSE:
The problem here is not that the Object Types are corrupted. The modifications to the object types are expected and essential.
The issue is that the new object types have not been created in the .cst file so that the AppBuilder does not know how to deal with them. The solution is to modify the .cst file.The problem here is not that the Object Types are corrupted. The modifications to the object types are expected and essential.
The issue is that the new object types have not been created in the .cst file so that the AppBuilder does not know how to deal with them. The solution is to modify the .cst file.
FIX:
Updating .cst File After DCU Upgrade
====================================
Upon using the DCU to upgrade to 2.0, new object types may have been created. Any new object types will be listed in the dcu.log file, located in the dcu start-in directory. If the upgraded objects have been converted to use these new object types, it will be necessary to add the appropriate .cst files in order to work with your migrated objects in the appBuilder.
It is recommended to create a new .cst file to handle the new customized object types.
Follow these steps:
1. Create a new text file in the src/template file called 'dyncustom.cst'
2. In the src/template directory, open the icfdyn.cst file in a separate editor.
3. If a new Independent window has been extended (DynObjc), copy the 5 .cst lines that specify the Independent Window from the icfdyn.cst to the dyncustom.cst file. (From the *NEW-CONTAINER line to the PROPERTY-SHEET line inclusive)
4. Modify the first line (*NEW-CONTAINER) and modify the description and replace the object type in brackets with the new extended object type. (i.e. Replace: Independent Window (DynObjc) With: Independent Window (DynObjc_SITE_2967) ) It is important that the '*NEW-CONTAINER' name is unique for all objects in all of the .cst files.
5. Modify the line containing the 'TYPE' identifier and replace the type with the new extended type as specified in the dcu.log file (i.e. Replace: DynObjc With: DynObjc_SITE_2967) ).
6. Repeat steps 3 to 5 for all other new object types that have been created and save the text file. Make sure there is a blank line between every object and also ensure that there are no blank spaces on column 1.
Example:
*NEW-CONTAINER Independent Window Extended(DynObjc_SITE_2967)
NEW-TEMPLATE src/adm2/template/dynobjc.w
TYPE DynObjc_SITE_2967
IMAGE-FILE adeicon/smartwindow.bmp
PROPERTY-SHEET ry/prc/rycblnchrp.p
*NEW-SMARTOBJECT Dynamic SmartData&Viewer Extended(DynView_SITE_2967)
NEW-TEMPLATE ry/obj/rydynvwwizw.w
TYPE DynView_SITE_2967
7. This new 'dyncustom.cst' file must be deployed to all developers who will be using these objects. In the 'Use Custom' menu option from the palette, select the 'Add' button and add the dyncustom.cst file to the list of custom object files. Use the 'Move Up' button to place it directly below the 'icfdyn.cst' file.
8. Select the 'Option' menu option from the palette and then select 'Save Palette'. This will create a new entry in the registry (or ini file) called 'CustomObjectFilesICF' which will contain a delimited list of the .cst files.
Note: This will not be necessary after version 2.1, as the information within the .cst files will be merged into the repository.