Hi Walter,

>I fully agree. People can workarround this issue two ways:
>1. Use the m. notation
>2. Avoid conflict with field reference

Except 2. can only work if you name all your fields. If you write code that you expect to work in any environment, m. is the only solution.

I must say I completely agree with many of your thoughts--programmers need to understand what they are doing and why it works. That's why I find your m. position inconsistent with your other rational.

To all the standards folks, I hope that you use names are compelling and meaningful. I use only one global variable, ThisApp. I sometimes use a private, ThisReport. (I think Craig suggested one of those in a post years ago.) It would be so stupid for the main global variable to be named gThisApp, wouldn't it?