>>>>> The reason I never use a prefix m. before a variable is because I am always careful in naming my variables different from fields or expression.
>>>
>>>Just a head's up that m. on the right side of an = avoids VFP checking for a field of that name in the selected table/cursor. This can cause visible performance differences in SCANs or loops where the selected cursor has lots of fields. Therefore I try to use m. on the right side of an =.
>>>
>>>Whereas on the left side of an =, m. is not necessary (as it has to be a variable- a field would need REPLACE or UPDATE) and also slightly decreases performance.
>>
>>Thank you for your input. How do you know how VFP works "under the hood"?
>
>To add to John's response, I did my own testing a few years ago about how much mdots matter for speed:
http://www.tomorrowssolutionsllc.com/Articles/Use%20MDOTs%20for%20speed.pdf.
>
>Using mdots where they make a difference is absolutely faster.
>
>Tamar
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham