>>>>SNIP
>>>>
>>>>>Why do that when it is not necessary, but ignore mdot when it certainly can be necessary?
>>>>
>>>>If you find yourself that it is necessary, it already is an indication there is something wrong. Column names should not conflict variable names in the first place. Granted, there are situations where this is out of your control, but in general your naming conventions should avoid this at all cost.
>>>>
>>>>To answer your question directly. For me it affects readability. As like Lutz, I hate it passionately.
>>>
>>>I don't care what you personally think or do. FoxPro works that way.
>>
>>That is a nonsensical answer. Coding practices have very little to do with how a product was designed. The latter is a human readable representation of instructions to the mechanics in the programming language.
>>
>>The fox isn't flawless. With the knowledge we have now it would not have been build in the same way as it is. There is a reason there is a good portion of commands and functions that are not commonly used anymore. The mdot would certainly not be part of VFP if it would not rely on its heritage.
>>
>>So I have no idea, what your implying when you say "FoxPro works that way".
>
>Do you believe that repeating yourself many times will change people's opinion? :-)

Its not my intention to convince mike. I've given up on that, many, many years ago. However, I still have a little more hope others get the point that applying naming conventions is crucial for improving code readability and avoiding creating bugs, whether or not related to mdot.