>>>>>>No we come to the statement I wrote earlier:
>>>>>> forcing naming conventions for fields are incredibly easy... For variables they are a lot harder... for applying mdot properly and consistently near impossible for mortals programmers.
>>>>>
>>>>>This is the key point. You think it's easier to enforce naming conventions (and, for that matter, to have naming conventions that ensure there's never a conflict). Others think it's easier to use mdot.
>>>>>
>>>>>Pretty sure we all agree that people will make mistakes (and just to prove it, when I first typed that word, it came out "mistkaes"). You seem to believe that recovering from a naming mistake is easier than recovering from an mdot mistake. I disagree, since recovering from a naming mistake will often require changing multiple lines of code.
>>>>
>>>>In all likelyhood, you'll have to type a variable multiple times in your code (or hence what is the purpose of it?), so if there is something wrong with the variablename, there are multiple occasions to spot and correct it. If there is a name mismatch you'll catching during testing. The cause of the naming variables wrongly, ussually is developers deliberately not following the convention, for which you can slap them in their fingers.
>>>>
>>>>with mdot the mistake could be in one spot and you might never catch it because it does not raise an error. And often it is forgotten by accident.
>>>>
>>>>Which part of the above do you disagree with ?
>>>>
>>>
>>>I disagree that you'll necessarily find the naming mistake in testing. As with a missing mdot, you may never find if it it doesn't raise an error.
>>
>>Lets clarify this. Making a typo in a variable is possible and you're right you might not catch that in all cirumstances, but this irregardless on whether you use mdot or not. So lets ignore this scenario.
>>What I was refering to is making a mistake in naming the variable. For example
>>
>>Name
>>
>>vs
>>
>>cName
>>
>>And use that variable mutiple times in code.
>>
>>
>>How likely is this done by accident as opposed to forgetting an mdot any time this variable is used?
>
>Both of you wrong. Both of these are dangerious. I think that's silliest thing in VFP with public, private, local issue. In first stage they had should to force use table name with fields like myTable.myField


Metin,

I'm affraid I don't quite get what you're trying to say.

Walter,