wfcreate
Posted: Tue May 25, 2010 2:17 pm
I am running eviews 7.1 and I am up to date with updates.
I have a header file in which I specify a path, the forecast version, and (ideally) the number of datalines being read in from an excel sheet.
If I explicitly specify 43787 unstructured lines as in: (Case 1: this works)
the workfile creates without a hitch; however, if I attempt to include the number of lines in my header file as
when I execute the wfcreate command I get an Illegal Date error: (Case 2: this fails)
My include statement is called beforehand. The program runs with no errors if I specifcy the 43787 as the number of observations.
I have tested at the command line and the illegal date error occurs again, however in the popup, it says !cur_vlen in the number of observations field, meaning it seems to take it as a string literal instead of as a numeric variable I was hoping it would think it should be.
Is it a Bug, a feature, or am I doing it wrong?
I have a header file in which I specify a path, the forecast version, and (ideally) the number of datalines being read in from an excel sheet.
If I explicitly specify 43787 unstructured lines as in: (Case 1: this works)
Code: Select all
wfcreate(wf={%netpath}\test\raw_fcst_{%cur_ver}.wf1,page=Raw) u 43787 Code: Select all
'# Current & Previous Forecasts
%cur_ver="0510"
!cur_vlen = 43787 'length of datafileCode: Select all
wfcreate(wf={%netpath}\test\raw_fcst_{%cur_ver}.wf1,page=Raw) u !cur_vlen I have tested at the command line and the illegal date error occurs again, however in the popup, it says !cur_vlen in the number of observations field, meaning it seems to take it as a string literal instead of as a numeric variable I was hoping it would think it should be.
Is it a Bug, a feature, or am I doing it wrong?