Right!

http://fox.wikis.com/wc.dll?Wiki~EssentialMDot~VFP

>>It was used extensively in older code when people did SCATTER MEMVAR and needed to make sure the variable was used and not the field. Today, m. is rarely used.
>
>I think some people would disagree.
>
>If you are writing black box code that has to be reliable, then using m. in front of all variable references will ensure that you access the variable you expect to. Unexpected table names could cause havoc. Someone might have a table named goAPP for example!
>
>Also some people have reported speed increases when using m. - presumably because VFP doesn't have to check the context to see if it's a workarea a-l, or a field, or a variable.