>>>IMO, mdot is largely a matter of VFP folklore. Wake me up when it gets to Fox vs Clipper, or even better, Spectrum vs Commodore.
>>
>>Now you are allowed to guess the side I choose.
>>;)
>
>Fine. Be stupid. I inherited lots of supposedly genius programmers over the years. All that allowed me to function was using m. as needed by the compiler. I currently have a table called latest. It is opened by a query. Then a scatter name is used. Then they use m.latest.fieldname. So, there goes any possible use of m.arrayname.
>
>If I write a piece of code for you to use, it will not break because of your table/field naming conventions. If you give me a piece of code, I am certain it will. This is the real world, not your isolated bubble.

Even the GDI++ library which uses the mdot notation has problems. So if you claim your code won't ever clash with fieldnames, I think you are delusional at best. I've never seen any code of respectable length being immune to the problem. And I have seen a lot.