Kbase P126707: Opening OE Architect results in errors because Form classes cannot be found
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
06/10/2009 |
|
Status: Unverified
SYMPTOM(s):
Opening OE Architect results in errors because Form classes cannot be found
The designer could not be shown for this file because none of the classes within it can be designed.
Could not load myMDIForm.cls
Cannot create/load the root component
Check syntax on the Architect generated source fails with invalid datatype error.
Syntax check:
Invalid datatype specified:
Infragistics.Win.UltraWinExplorerBar.UltraExplorerBar. Specify a datatype such as 'character' or the name of a class. (5638)
Invalid datatype specified:
Infragistics.Win.<control name>. Specify a datatype such as 'character' or the name of a class. (5638)
** Could not understand line <number>. (196)
Creating a new MDI Form and then adding some Infragistics controls.
Restarting OpenEdge Architect after saving new MDI form displays errors.
FACT(s) (Environment):
Windows
OpenEdge 10.2A
CAUSE:
The assemblies.xml file that the session is using at startup is invalid. This could be from a previous installation and is being used because of an incorrect propath setting.
From a OpenEdge Architect session the assemblies file is searched for using the propath. If it is found, then that one is used to write to at design time. If it isn't found in the propath, then a new one is created in the project root directory, and the PVM is told to load any new assemblies from that new file. The project root may or may not actually be in your propath.
FIX:
Modify the propath so that the correct assemblies.xml file can be found.