>I think some people would disagree.

I'll agree to agree with you on this. *G*... however, with datasessions, views, cursors, etc used for databinding, you see much less use of m. as in the Fox2x days when people did SCATTER MEMVAR.

>
>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.

I think the test results are mixed. I've seen tests where speed is improved, some where it is not, and others where the difference is so small, it doesn't matter.