>>>My opinion on mdot is that it rarely matters, it's useful only as a method to invoke intellisense in the command window, the trouble that may be caused by not using it is easy avoid and yep it looks ugly. Where do I pay my excommunication fees?
>>
>>It matters to me because of all the crappy coders I've encountered. Do not give anyone the right to say my evidence is ill advised.
>
>Do you hear yourself? You are basing the axioms of your coding religion on this crap. Find a better base.
>
>>In this very app I'm struggling with now, they do this...
>>
>>select alias
>>scatter name alias.
>>m.alias.property = something.
>
>Ouch.
>But, know what, in your case I'd take the time and replace this with
>

   scatter name scAlias
>   scAlias.property...

>and group mentions of scAlias in a with-endwith block where it makes sense. The scope of the scattered object can't be too big... unless it's a private variable mentioned in a dozen called methods/procedures, then I'd probably hire a couple of thugs to find the guy.

This approach is throughout the application. I cannot change the names of the "data objects" all over. They used it exactly like a cursor. My whole point is I use mdot as needed. None of the people they tried to hire ever even say m.alias.property. The original coder is dead. There is lots of room for improvement. It cannot be maintained without mdots, despite Walter's insistence that I am wrong.