>I know it works <g> But the point was that in our profile logic we had it
>in "fld1 between 100 and 200" form, which doesn't work with evaluate. Well, we went into User Maintenance form in production and changed all profiles to be in the "evaluate-friendly" form, but I also wanted to make sure I would not have such problem in the future. See my reply to Sergey with the current code implementation with try/catch and what do you think about it.

I think you should move try/catch and evaluate into User Maintenance form to validate the expression on save.