Fabio,

I misunderstood, thinking that you want to change the way that VFP looks for at variables not referenced by Mdot. But if I understand correctly, you want a setting to force using Mdot to reference variables. For me that would be no problem, though not necessary as that is my normal practice anyway, but for many who think Mdot is ugly or unnecessary for whatever reason I can't see them supporting that as any kind of enhancement or new feature.

>Hi Elmer,
>
>this SET or SYS it makes the opposite one.
>
>If active this new setting in VFP:
>

>?  xx && search on fields only
>?  m.xx && search on memvar only
>

>
>This modality is compatible with the current programs
>(now you cannot use m.fieldname where m it is a alias),
> only forces the developer to insert m. for get a variable value.
>
>It exists an incompatible situation,
>but i think that nearly nobody uses it:
> to use the value of a variable one in the case not is a field with the same name.
>
>A way soft to use it:
>active it in development phase,
>therefore it has been guaranteed that all the variable ones are not ambiguous,
>and disable it to runtime.
>
>Fabio