Feedback
Did this article resolve your question/issue?

   

Article

adecomm/adestds.i file cannot be found when trying to compile proedit.p

« Go Back

Information

 
Titleadecomm/adestds.i file cannot be found when trying to compile proedit.p
URL NameP87529
Article Number000152894
EnvironmentProgress 9.1D
Question/Problem Description
adecomm/adestds.i file cannot be found when trying to compile proedit.p
** "adecomm/adestds.i" was not found. (293)
** "<file-name>" was not found. (293)
** <program> Could not understand line <number>. (193)
** adeedit.p Could not understand line 83. (193)
** <program> Could not understand line <number>. (198)
** adeedit.p Could not understand line 84. (198)
** Unknown Field or Variable name - <field-name>. (201)
** Unknown Field or Variable name - initialized_adestds. (201)
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
The include files required for the compilation cannot be found because they reside in the adecomm.pl library.
Resolution
To compile the Editor the adecomm.pl library needs to be extracted to a local src directory below the working directory. So, after extraction the files should reside in the directory <working directory>\src\adecomm. The compilation of the editor will then work.

This is documented in the Managing ABL Applications manual with the following note:

Note: OpenEdge can only find r-code members in a procedure library. While it is technically possible to include other types of files in a procedure library, OpenEdge cannot find them while searching the PROPATH.
Workaround
Notes
References to Written Documentation:

OpenEdge Deployment: Managing ABL Applications, Chapter 6: "Managing Procedure Libraries"
Last Modified Date9/13/2015 11:53 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.