>Hi Alan,
>
>[snip]
>>
>>Forbidding something that you can't enforce has never worked in the past, so I don't hold out much hope for it in the future. When VFP itself forbids using 'This' as a field or alias name, then you can do as you say, but then again, when that happens, Fabio will be able to drop the 'm.' in front of 'This' with no change at all to his standards.
>
>Goal!.

Hey Fabio, are you the referee here? :)

>>>The standard should incorporate:
>>>- Never create a field with a reserved name like THIS.
>>>- Use the mdot in the right argument, but do not use them in front of reserved words like THIS.
>>
>>>I don't mind that Fabio uses m.this in his own code, although I would not like to read or maintain such code. But I think it's inappropriate that he uses that method here on the UT in his examples. It are the starters who get influenced. And it's a bad influence.
>>>
>>>Maybe we can vote on THIS ...
>>
>>I vote that Microsoft prohibit the use of 'This' as a field or alias name. Then... problem solved.
>
>I add another vote ( and this will have as side effect also one small performance increment )

Also add my vote. So, no disagreement on this one.