Using "m." creates an unambiguos statement for someone else looking at your code. Whoever wrote the code at MS is aware of this. If you know noone else is ever, ever, ever going to look at your code, call variables whatever the heck you want. Create your own naming scheme if you so desire.

But if you're working with a team, anyone can look at your code, see the "m." and immediately know where the variable is from. The "lc", "ln", "gc" preface is additional info about the variable to let you know the type and visibility, but there's still no rule that you can't name a field with the preface.

Pf

>It's just now starting to sink in what you were saying there. Though feel free still please to wade thru VFP samples code expecially FoxIS and tell me what you think. If m. prevents referencing a develper's field that may be named the same as a variable then I can see its usage and learned something today. Still, I haven't seen anything close to the frequency of usage of m. that MS uses as compared with yours or others' work
>Thanks