July 20, 2005, 06:57 PM
Robin LovellBY HIGHEST n Error in 5.3.3
Came across a buglet today in 5.3.3 (Linux). It does not occur in 5.2.6 and it appears to be corrected, though undocumented, in 5.3.4.
It is reproducible, but does not happen every single time. BY HIGHEST/LOWEST fieldname does not give the error message; only BY HIGHEST/LOWEST n fieldname. Even though there is an error message, it still generates correct report output.
>>table file car sum car by highest 1 country
(FOC002) A WORD IS NOT RECOGNIZED: _T00000EDAPROF REPLY:
>end
NUMBER OF RECORDS IN TABLE= 10 LINES= 5
(BEFORE TOTAL TESTS)
PAGE 1
COUNTRY CAR
------- ---
W GERMANY BMW
July 21, 2005, 10:22 AM
Tony ARobin,
Executing the fex as a single line also fails on XP with the same error. This is true of command line or via fex.
TABLE FILE CAR SUM CAR BY HIGHEST 1 COUNTRY
END
However, split into several lines and it works OK.
TABLE FILE CAR
SUM CAR BY HIGHEST 1 COUNTRY
END
July 21, 2005, 01:05 PM
Robin LovellTony,
Yes, I get the same in Linux. I just tried this and it doesn't seem to matter where you split the line.
In addition, once it has run error-free with a split line, subsequent executions (in the same Focus session) with a single line do not generate the error message.
Ain't Focus' foibles fun?
Robin