Kbase P126284: How do compile time arguments work?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/12/2008 |
|
Status: Verified
SYMPTOM(s):
Compile arguments to RUN statement supplied, but could not find '%s'.
** "<file-name>" was not found. (293)
FACT(s) (Environment):
All Supported Operating Systems
Products / Versions
CAUSE:
When running a compiled 4GL/ABL program with either intentional or unintentional extra characters on the same line as the RUN statement after all valid parameter and procedure information these errors might occur. The 4GL/ABL allows compile arguments to be passed to procedures when compiling code 'on the fly'. This is only useful for external procedures and will cause different errors when used with internal procedures.
Example:
RUN foo.p ( INPUT cInput ) "bar".
The string "bar" in the above example is taken as a compile argument when foo.p is executed. The problem occurs when running foo.r and foo.p doesn't exist in the propath. The runtime automatically looks for the corresponding source code file, in order to recompile it with the argument, and when it cannot find it one of the above errors are returned.
FIX:
- If the code was designed to intentionally pass compile arguments, ensure that the source code is available in the propath
- If the characters on the line were unintentional or were the result of some type of truncation, either remove them or place them on another line.