Hi Fabio,

understood: VFP will never look for a field on the left hand side of the = operator, as there is no way to assign a value to a field. So this code also does not raise an error:

CREATE CURSOR curTest (cField c(1))
cField = 1

As I've seen you also were gaining performance with STORE vs. = in another posting here...

tt = SECONDS()
FOR lnCount = 1 TO 1000000
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
    store m.lnMemvar To lnMemvar
ENDFOR
? SECONDS()-m.tt

The reason may be that vfp now doesn't have to decide what is meant by "=", an assignment or comparison operation. I wonder why this isn't decided at compile time. I don't see me coding STORE from now on just because it's faster.

Bye, Olaf.