It would be nice if IBI would make the IBFS pathing scheme acccept * as a reference to the location of the referencing file (i.e., when file A references file X and the path to X contains *, the full path to X will be calculated using the full path to A to supply the missing qualifiers).

Then a parent and its co-located children could be copied or moved amongst Repository folders without issue.

Hi j.gross,

Please open a New Feature Request for this functionality on InfoResponse Online.

Thanks and regards,

Kathryn

quote:

-MRNOEDIT -INCLUDE &I_DEF_FILE.EVAL

Has anyone been able to get an include to work using an amper variable with WF 8?

I have tried both

-INCLUDE &INCLUDE_VAR.EVAL

and

-MRNOEDIT -INCLUDE &INCLUDE_VAR.EVAL

and I get (FOC2905) &VARIABLE IS NOT ALLOWED AS A FILENAME IN THIS CONTEXT:
&INCLUDE_VAR.EVAL ;

Your first line of code,
-INCLUDE &INCLUDE_VAR.EVAL
(sans -MRNOEDIT) is syntactically an MR include, and will be rejected. MR does not execute your fex code, it just performs a static analysis, looking for lines that it has to modify (and/or take special action to support). Thus, MR has to stop the music, since it cannot forward the referenced MR fex file.


In your second line of code, when MR sees

-MRNOEDIT -INCLUDE &INCLUDE_VAR.EVAL

it strips off the -MRNOEDIT, and passes the rest through to the Reporting Server without change. So far so good.

Before execution, the Reporting Server scans the code - performing a static analysis (akin to MR's) to see whether it should issue an Autoprompt. Whenthe scan encounters

-INCLUDE &INCLUDE_VAR.EVAL

he complains that it cannot scan the included fex for unresolved amper vars (since at that point he, too, does not know what value the amper var will contain) -- that's when the FOC2905 is issued.

(If you turn off autoprompting, you should not get the FOC2905).

BUT then the Reporting Server will (in my experience) proceed to execute the code, and in execution the -INCLUDE in that form is perfectly ok (it's even a recommended practice -- per DN 4501181.0114 "Developing Reporting Applications [8.0.070]", p 392]).

By the way, the .EVAL is unnecessary.

Hi All,

Relative pathing is not supported in WebFOCUS 8. While it may work in some scenarios, it won't work in all.

There is a New Feature Request in programming to add the ability to use relative pathing, but it has not yet been implemented.

Currently, only absolute pathing is supported.

Thanks and regards,

Kathryn

This message has been edited. Last edited by: <Kathryn Henning>,