>>>>With VFP8 "m" stands for more than just 'memory variable'. From the VFP8 Help for SCATTER: "To reference a property in an object that has the same name as an open table, preface the property name with the m. qualifier.". So it now can pertain to properties too.
>>>
>>>
>>>
>>>Which, of course, is because properties are also just memory variables.
>>
>>I knew someone would come with that statement. But it ain't so, else we never would have called properties properties in the first place.
>>Just because properties reside in memory doesn't make them memvars. Else fields are memvars too, because they too are in memory.
>
>
>Who is "we" ?
>Are you a member of the VFP developer team ?

Not likely! We is US, people who develop with VFP. If MS has chosen to call something a "property" when it had no substantial difference from a memvar I think we'd see many (most?) calling them 'memvar' regardless.
Too bad we can't do the reverse, at least as far as the (MS) usage of "cursor" in VFP is concerned.