>>>Hi.
>>>
>>>does it make any sense to have mdot used like this
>>>

>>>m.ObjName1.Name2()
>>>

>>>?
>>
>>mDot is how FoxPro works. Computers are fast but stupid. If you can deliberately tell Fox what is a memvar vs a column, your code is clearer. The speed gain can be significant at times. Why not get it for free. It is nothing to do with personal preference.
>
>Preference for the mdot expansion on IntellisenceX. This I hate passionately.
>For the rest. The question is, does it make any sense for this specific construct. It simply could not by a table field (That's what you name column?). So it must be a variable. Same goes to array. If a ( or [ occurs, it's simply not a field or table.field

The array is not a memvar at all. It's more of a structure. The object is a memvar. It simply could not be a table field/column? Oh yes it can. I can make a column called A or a variable called A. We have the intelligence. Computers do not. Don't let them spend time figuring things out. Tell them.

Many people write this:

select alias
replace alias.fieldname with value.

The alias in the replace line is rarely needed, but everyone seems to want to put it because, as they say it is safer. Why do that when it is not necessary, but ignore mdot when it certainly can be necessary?