Kbase 20372: ADM2. Running ADM 2.0 Code With Version 9.1x Generates Error 6439
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.x
SYMPTOM(s):
ADM2. Procedure <procedure> has no SUPER procedure with internal procedure <internal-procedure>. (6439)
CHANGE:
Migrating ADM2 application from Progress 9.0x ADM2.0 to Progress 9.1x ADM2.1
CAUSE:
Progress r-code that is compiled in a Progress release such as Version 9.0A or 9.0B is expected to run successfully without recompilation in a later release within the same version number, such as Version 9.1A.
This includes Smart Object Applications.
Bear in mind that the ADM consists of a body of 4GL code, some of it in compiled objects such as super procedures, and some of it in include files.
Obviously it is not possible for a Smart Object application to see enhancements to the ADM or bug fixes in this 4GL code without a recompile of the application.
FIX:
You have two choices to make the code work in Version 9.1x:
- Recompile with Version 9.1x.
Recompilation allows you to take advantage of the enhancements in ADM 2.1. The process requires you to resolve any discrepancies between customizations you might have made to the earlier ADM code and the new versions of the ADM code
that is shipped with the new release.
- Copy the Version 9.0x ADM with your application code to Version 9.1x.
You do not have to recompile if you use this technique. Keep all compiled application objects (including the compiled super procedures and any other support procedures from the earlier release) then run the application on the new Progress executable without using any of the new ADM 2.1 code.
NOTE: The maintenance of code from an earlier Progress version within the Version 9.1A AppBuilder is not supported because of dependencies between the AppBuilder and code that supports the ADM.