>Yes, it's bug fix. In VFP8 everything after CHR(13) is ignored in EVALUATE().

This is not true:

run on VFP8:

? LEN(EVALUATE("[1"+CHR(13)+"2]")) && NO ERROR AND 2 is not ignored
? LEN(EVALUATE("[1"+CHR(10)+"2]")) && FIRE ERROR

I use CHR(13) on 3000 evaluated scripts without problems on VFP8!

>IN VFP9 CHR(13) is treated the same way as CHR(10) which generates an error in VFP8.
>I'm not sure what you mean about 'execute incomplete code'.

It means what you have said.

I say that VFPT have fixed the CHR(13) within a inner string of the evaluated string, but not into the evaluate string one,
then the issue to which you refer is remained unsolved.

Run:

x="trx(1)"+CHR(13)+"trx(2)" && ignore trx(2) and no errors on VFP8 and 9
EVALUATE(x)
x="trx(1)"+CHR(10)+"trx(2)" && ignore trx(2) and no errors on VFP8 and 9
EVALUATE(x)

PROCEDURE trx(z)
 ? z
 RETURN 

No gain, only dangerous for me.

Fabio