>I keep running across examples of code that occasionally prefix variables with m. (ie. m.nTablesUsed = AUSED(aTablesUsed))
>
>I've been trying to figure out what the signifigance of the m. is in the context of the code, but it's hasn't clicked yet. All of the books I've been reading provide examples of code using it, but none have explained the purpose. (My guess is that's it's so elementary they didn't think it needed to be explained, which may be true, but there are always a few in the crowd that happen to be more dense than the rest =)
>Can somebody please enlighten me? (Or, if it's a lengthy explanation, point me to documentation...)
>
>Thanks!

Here's a bit more information.

m. is never needed on the left side of an equal sign because you can never have a field name there. In fact, using an m. on the left side of the equal sign slows down processing that line of code by as much as 3 times. This has been true since at least the 2.0 days (I didn't test with versions before that). Some people say "Big deal..one line of code", but if you have many lines of code written that way, it can severely slow down your application.