P>Srdjan,
>
>But this is already well known by VFP and it has the "m." to take care of it.

As I said, I understood what is happening and I took care of it
point is that one error message would make all the difference ...

Perhaps u hv code builded up in the functions and classes (framework developed years ago) and all of sudden u run across table that HAVE to have field(s) named this way. Even if u used m.xx all along u would still run into problems when u deal with scatter/gather constructions to populate data - again u will run into problems as I will show in this example:

local   m.lLocal
private m.lPrivate
public  m.lPublic

store .t. to m.lLocal , m.lPrivate  , m.lPublic

=form_call()

if m.lLocal = .t.
    wait wind 'Local ok'
else
    wait wind 'Local not ok'
endif

if m.lPublic = .t.
    wait wind 'Public ok'
else
    wait wind 'Public not ok'
endif

if m.lPrivate = .t.
    wait wind 'Private ok'
else
    wait wind 'Private not ok'
endif


function form_call
    create cursor test ( lLocal L, lPrivate L , lPublic L )
    append blank
    scatter memvar     

Even If we leave aside code purity & speed for the moment
we still hv problem!
Code flow gets influences from 'outer space'
without any warning !

I just don't like it :)