If you have a variable and a field (in the current work area) which both have the same name, the field takes precedence.
"m." forces VFP to use the variable, even if there is a field. Even if there is no such field, it is also supposed to be somewhat faster to use "m.", since VFP doesn't need to check if there is a field.
For comparison:
client.clientcode refers to field "clientcode" in table "client" (more accurately, in the
alias called "client").
a.clientcode refers to the field in the first work area. This works for the first 10 letters of the alphabet, but this syntax is not recommended.
>Hi,
>
>Excuse my ignorance, but I've been constantly encountering code in UT with a variable preceded with an ".m", like below:
>
>
>ldFrom = MIN(m.tdFrom,m.tdTo)
>
>
>What is ".m" ?
>
>Thanks in advance.
>
>Steve
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
