>>That is right. If you inherit a system where those rules were applied and a rewrite isn't an option, applying mdot is the only reasonable thing left to do. But its an ill advice to start building a new system using the same naming conventions for fields and variables, force the use of mdot and rely on old relics like scatter memvar.
>
>As I mentioned rhetoric replying to Mike, I consider grouping mDot usage together with /at same level as "scatter memvar" as unworthy rhetoric.

How so? as this was the common way to do things in Fox2.x. In fact scatter name was not added to the language before VFP6.