Kbase P12606: Suggestion for SYSTEM ERROR: fmeval: bad data type for function 0. (66)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/6/2009 |
|
Status: Verified
SYMPTOM(s):
Code failing with error 66
SYSTEM ERROR: fmeval: bad data type for function 0. (66)
SYSTEM ERROR: fmeval: bad data type for function <function>. (66)
Stack Trace reads:
uttrace
utcore
drexit
msgout
msgn
fmEPLUS
fmeval
umxColorExpr <------ HERE
umFldClassReevalColor
CAUSE:
User Defined Functions (UDF's) could play an important role:
BGCOLOR a + b
... is legal syntax, therefore it's possible that the customer has something
of that sort in their code.
BGCOLOR is not the only option (you also have FGCOLOR), and not
necessarily at the frame level.
You could also have:
DEF VAR a AS INTE.
DEF VAR b AS INTE.
DEF VAR c AS CHAR.
FORM c FGCOLOR a + b
WITH FRAME f BGCOLOR 10 + b.
Both the foreground colour for variable c and the background colour for the
whole frame are expressions, and that might generated the problem.
It's even possible fo have UDF's (User-Defined Functions), therefore the
following is legal syntax:
DEF VAR a AS INTE.
DEF VAR b AS INTE.
DEF VAR c AS CHAR.
FUNCTION myUDF RETURNS INTEGER:
blah ...
END FUNCTION.
FORM c FGCOLOR a + b
WITH FRAME f BGCOLOR 10 + myUDF().
FIX:
Investigate the code with:
COMPILE failingProgram.p PREPROCESS failingProgram_preprocess.txt