>Hi Mike
>
>>>It's really funny. In the program that used by several developers my colleague put **** PLEASE DO NOT PLACE "m."s *** at the top and removed m. even from my procedures <g>
>>
>>That's not funny. That's plain stupid. Leaving them in will prevent errors and improve performance. Taking them out ONLY changes how the code looks in an insignificant way.
>
>I just jumped into this thread, so please forgive me if this is already brought up.
>
>What would happen when...
>

LOCAL lcMyVar
>
>lcMyVar = MyTable.cMyVar

>
>Is this efficient and still avoids the problems and improves performance?

Yes, it's efficient. I always add table aliases to avoid ambiguity. We're talking about lcVar = m.lcAnotherVar In this case m. indicates, that it's a memory variable and not a table field. Following strict naming convention reduces risk of running into table field to almost 0%. The performance difference would be visible only in lots of iterations...