>Hi Randy,
>
>The conflict between variables and fields is the most difficult bug to track. If the conflicting field and variable are of the same data type, the bug will undoubtedly be hidden. Code will not crash but will give wrong result. This can be a disaster for programmers.
>
>I don't think not using "m." in code will be a problem for experts like Walter and George. But for average programmers, this can be a horrible trap.
>
>Looking at the December issue of FoxTalk, you are the only writer who put "m." in code. Your article really helps the community to promote the "m." practice, which will be beneficial to VFP learners.
>
>Ben

I agree, in fact an optimal thing would be a new SET os SYS()
that force VFP to does not search a variable without m. prefixe declared.

SET MEMVARPREFIXNEED [ON|OFF] && defaul OFF
* or
SYS(someNumber,0|1)  && default 0

Fabio