>Hi Fabio,
>
>This is a documentation bug, I'd say. The documentation should add that NORMALIZE() stops when it encounters the end of the expression and ignores any remaining characters.

Hi Christof,

this can to be, but I am in discord with this design.

I do not want that NORMALIZE() ignores an expression piece when valid expression has found one,
and that none evaluation comes made. Instead it evaluate ( reduce ) the expression!
Doc:
The syntax of any Visual FoxPro commands or functions within the character expression is checked, although the expression is not evaluated.

? NORMALIZE([2+3]) && evaluated !
? NORMALIZE([2+x]) && not evaluated
? NORMALIZE([&x])  && this is a correct expression and fire a error
? NORMALIZE([2+x/])&& fire for a missing operand
? NORMALIZE([2+x(])&& fire a error
? NORMALIZE([2+2(])&& don't fire a error
SET POINT TO '%'
? NORMALIZE([2.3]) && format a Number for output !
? NORMALIZE([2.A]) && ignore the A

To this point, for me NORMALIZE() is inusabile.

You know a reasonable way to use NORMALIZE() ?

Thanks
Fabio