>Hi Fabio,
>
>>

>>? varCash
>>

>
>Whether or not to use m. is not a rule but a personal preference.
>I've got other rules to make it clear whether it is a field or variable:
>
>Variable:
>Prefixed with a type character (eg: cString, nCount, lUsed, dDate)
>
>Field:
>Prefixed with three characters identifying the table (eg: prs_pk, Prs_firstname, prs_lastname)
>
>IOW, In my programs there is no question whether we talk about a field or variable.
>
>>

>>correctness and formal precision
>>

>
>I've got trouble with this as there are quite a few arbitrary rules when to use or not to use m. Those who apply m. themselves have different rules where and when to apply them as wel. Some say it is not neccesary at a variable assignment while other say you must be consistent and apply them where you can. It does not make sense to me. I just don't use them unless neccesary for whatever reason.
>
>Walter,


Hi Walter

Sorry, but you are mistaking, the convention of the names, performance or any other thing, does not have any importance, it is a VFP rule.

Ill-fatedly, all the documentation of VFP, programs and articles suffers from laziness and approximation, and the brace laziness and approximation they diffuse more quickly than a virus.

Walter, I have confidence that you do not take it as I face staff, the my esteem in yours confront remain unchanged.


Fabio