>>Hi Mike,
>>
>>Thanks for the advice on using the m.lcVar instead of "&". I'm used to using it (&) in clipper programming, but now I know it has different results with VFP9. Just wondering what's the use of "m." in m.lcVar?
>>
>>Thanks again and I hope I'm not asking too much for advices. All your help are greatly appreaciated.
>>
>>Sonny
>
>It's been a very long time since I programmed in Clipper, but I thought & was a macro expansion of the same type as dBase III. I'm not up to VFP 9 yet, but I didn't think anything significant had changed with macro expansion from any of the earlier versions of xBase.
>
>As far as "m." goes, it is an indication that the name following it is a memory variable rather than a field name. If there is a field of the same name in your currently open work area, the field takes precedence unless you've explicitly used "m."

It is safer and faster to use m. regardless of hungarian naming conventions, nor how the code "looks".