>m.MyVar = 3
>
>is 3 times slower than
>
>MyVar = 3
>
>I've tested this in every version since 2.0 and the results are consistant. Some people argue that putting m. on the left-hand side makes it clear that it is a variable and will make sure that a variable is used instead of a field. This agruement doesn't hold water. You can't use a field on the left side of an equals.

Oh, cool! I love it when someone tells me I'm already doing the smart thing.

Some people have said they don't need scope letters anymore because they never use private variables but your point above is sufficient reason to use a scope prefix.

IOW, if my tables looks like this:

TABLE.iKey
TABLE.cCharacter
TABLE.nNumber
TABLE.dDate

and my variables look like this:

local liKey, lcCharacter, lnNumber, ldDate

then there will never be any ambiguity in referencing a variable or a field.



Thanks for all the suggestions.

Peter