>>This has bitten me so many times so now I always use INT() just to be safe.
>
>Yes, I'd say it'd have to be improve in the next version.

I don't think that's good idea because it could break existing code and there's an easy fix.

>But, at one time, doing lnNumero=VAL(lnNumero) generated an error even if lnNumero was equal to 1.00.

Yea, VAL() functin had it share of bugs and it stil does. Try ? VAL(-$10)