>>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.
>
>Okay, internally it might be a structure - I do not care from my POV. It's something not a related to a cursor or related to an object in a method like THIS[FROM[SET]], I call it a variable, because I can alter with = or STORE.
>
>

>CREATE CURSOR muh (lax I)
>INSERT INTO muh values(1)
>DIMENSION lax(1)
>?lax(1)  && array cell
>?lax[1]  && array cell
>?lax	&&field
>?lax	&&field
>?m.lax  && array cell
>

and yet lax=1 fills the entire array with 1. Who thought that would be nice? Why can't I have m.lax as a var and lax[1] as a cell? So I don't consider an array a single variable, but a structure of vars. I never refer to an array like a var.


>
>Array access does not need mdot, so it's superflous
>>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?
>
>Other people use waistband, belt and a pair of braces together - this only defines them as overcautious
>

>select alias
>replace alias.fieldname with value IN alias
>

>
>Even if we assume that some crappy coded event alters workarea in the middle of the code, this is not good coding.