Using environmental variables in dataexport calc

Question

I'm using 11.1.2.1, and I thought I'd try this fancy new feature of using environmental variables in a DATAEXPORT calc script.
I've played around quite a bit, and believe the following is true.
The environmental variables must be the full path (including file name), that the export will write to.
Assume the following:
$DATAPATH = C:\data
$FILEPATH = C:\data\export.txt
If you try to export to $DATAPATH, it will error because there is no file name associated with that path.
If you try to export to $FILEPATH, it will work just fine.
Doesn't this kind of defeat the purpose of using environmental variables if you need a different variable for each file name?
My hope was that it worked like this:
Assume the following:
$DATAPATH = C:\data
In our export calc, you could append values that are specific to that calc/app.
e.g.
For an App 1 Export:
DATAEXPORT "File" "|" $DATAPATH/App1/filename.txt;
For an App 2 Export:
DATAEXPORT "File" "|" $DATAPATH/App2/filename.txt;
Am I missing something here? Any input both confirming/denying the above is welcome.

Answer 1

The dataexport command is very fussy about the file path as you have found out it only works you place the full path/filename in a variable.
It is also possible to use substitution variables but once again I think you need to use the full path/filename - Re: MaxL with DATAEXPORT and passed parameters
Cheers
John
http://john-goodwin.blogspot.com/