Kbase P15229: Why can .p, .i, and .w files be placed in a procedure librar
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/25/2003 |
|
Status: Unverified
FACT(s) (Environment):
Operating System
FACT(s) (Environment):
Progress/WebSpeed Versions
SYMPTOM(s):
Why can .p, .i, and .w files be placed in a procedure library file but, they cannot be run?
Progress documentation states "Progress will not look for source code in a
procedure library".
FIX:
Although .P .I & .W's can be added to a procedure library this is only meant as a method for centralizing information in your development and deployment directory heirarchy.
The best example of this is how Progress packages all of it's tutorial samples within the adecomm.pl as well as other libraries. These files can then be extracted one at a time with the -yank command or all at once with the -extract command.
However you can run .r code from within a procedure library that is in your PROPATH. For more information on this please refer to the Client Deployment Guide.