Yep, this isn't religion (although some people certainly act like it is) and I'm not trying to convert anybody ;)
>Mike,
>I agree it is a habit that I use m. for variables and alias.fieldname for fields. And I do realize that there are many places where I use it that it is not really necessary. And I do realize that there are instances where it cannot be used. Like, even though and array is like a memvar, you cannot use m.arrayname to reference an array unless "M" represents an object that has a array property. Or when using a variable in macro substitution. But that is just about all that I can come up with off the top of my head where it is not allowed.
>
>This is no different than using some of the optional key words like TYPE in "COPY TO filename.xls TYPE XLS", or using "NEXT" instead of "ENDFOR" to specify a FOR ... ENDFOR loop
>
>I am not is saying that you are wrong or I am right. It is really a matter of programming style and conventions and what works for you. My point is that for me and others reading my code, it does make it more readable and it does not appear to significantly slow down processing.
>
>After all, most people reading your source code don't understand what is so difficult about computer programming anyway. It is just a bunch of typing with mostly mispelled words, incomplete sentences and misuse of puncuation marks;}
>
>Cheers
>Elmer