Kbase P118552: Trying to use an earlier version of the ADM with a later version of the AppBuilder fails with errors
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/3/2008 |
|
Status: Verified
SYMPTOM(s):
Trying to use an earlier version of the ADM with a later version of the AppBuilder fails with errors.
Property <property> not defined.
Property ModifyFields not defined.
Property EnabledObjFldsToDisable not defined.
User-defined function '<function>' invoked dynamically but could not be found. (5639)
User-defined function 'setLogicalObjectName' invoked dynamically but could not be found. (5639)
User-defined function 'adeuib/_vgenrl.w' invoked dynamically but could not be found. (5639)
FACT(s) (Environment):
Using a 9.1B version of the ADM2 with the 10.1A AppBuilder
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
CAUSE:
The Property Sheets and windows of the AppBuilder have been compiled to include the properties and methods of the AppBuilder version. Earlier versions of the ADM will not include these properties which have been added to a later product release. Subsequently Development using a different (earlier) version could result in property errors.
FIX:
This is not a supported method of Development. Earlier versions of the ADM can be used for compilation and deployment, but Development must be done in the same version of the AppBuilder as the ADM. If further enhancements need to be made to the current application they should be done with the version of the AppBuilder that created them. So if the application is written in 9.1B then the 9.1B AppBuilder should be used. Compilation and deployment can the be done with 10.1A using the 9.1B ADM2 code.
Although the best solution to this problem is to migrate the application correctly to the latest version of the ADM2.