Kbase P163502: OpenEdge Architect: Errors running and checking the syntax of an ABL procedure in the OpenEdge Edito
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/19/2010 |
|
Status: Unverified
SYMPTOM(s):
OpenEdge Architect: Errors running and checking the syntax of an ABL procedure in the OpenEdge Editor Perspective.
Exception occurred during launch
Reason: Could not find startup <file-name> in PROPATH
** "<file-name>" was not found. (293)
Exception occurred during launch
Reason: Could not find startup custom.p in PROPATH
** custom.i" was not found. (293)
The 'Exception occurred during launch...' error is generated when trying to run a newly created ABL procedure ( ' Run As OpenEdge Application ' ).
The ' ** custom.i" was not found. (293) ' error is generated when trying to check the syntax of a newly created ABL procedure that references an ABL include.
FACT(s) (Environment):
Both the ABL procedure and the ABL include were created in a new OpenEdge shared AVM Project.
The shared AVM Project was created by copying another Project connected to the same AVM using COPY, PASTE and RENAME.
Windows
OpenEdge 10.2B
CAUSE:
The above errors occur because the directory of the new OpenEdge shared AVM Project is not in the shared AVM PROPATH. When a new OpenEdge shared AVM Project is created by copying an existing Project connected to the same AVM using COPY, PASTE and RENAME, the directory of the new OpenEdge shared AVM Project is not automatically added to the shared AVM PROPATH.
CAUSE:
Bug# OE00196899
FIX:
The fact that the directory of the new OpenEdge shared AVM Project that is added using Copy and Paste is not automatically added to the shared AVM PROPATH is a bug. As a work around, add the directory of the thus created OpenEdge shared AVM Project by selecting the following:
Windows | Preferences | OpenEdge Architect | Shared AVM | PROPATH |Add External Directory.
and type or navigate to the new OpenEdge Project directory and click OK.