>>>>Karen,
>>>>
>>>>clearly there is some misunderstanding here. The thing is that m is a reserved word, since you can use it to tell that what comes after it plus a dot is variable, even though a field may have the same name. Like if you have opened a table with a field called XX with a value of 5, and a variable called XX with a value of 10. Now you see the following:

>>>>?5*XX && 25 since a field has precedence
>>>>?5*m.XX && 50 since m. tells VFP to use the variable XX.

>>>>Also note that m alone is not allowed as a variable name, and it's also not allowed as an alias. And a field named m would most likely be asking for real trouble,
>>>>
>>>
>>>>Also note that m alone is not allowed as a variable name
>>>> And a field named m would most likely be asking for real trouble,
>>>
>>>
>>>Says who ?
>>
>>Check Reserved Words in Help.
>
>
>There are (hardly) reserved words in foxpro, ie foxpro does not enforce them
>
>(reserved) words become significant, ahem reserved, in the context
>
>

>local if
>if = 2
>if if == 2
>	? 'if = 2'
>endif
>

If you want to live on the edge, try this, and play with the values.

Create Cursor _screen (height i, width i, left i, visible l)
Insert Into _screen (height, width, visible) Values (500,500,0,.t.)
Browse