>>Being stuck with the decisions of previous developers is exactly why I promote mdot.
>
>I do agree with you about mdot.
>
>I got burned in the early 90's and I forgot which version of Fox it was, but either Fox Software or MS shipped a little Fox based utility that you could add to your code to allow users to browse dbfs or something like that. Well, it worked great and my users loved it, but it would error out and die. It took me awhile to figure the problem out because the little browser tool worked perfectly on all of my app's tables except for one. My table had a field with a name that they used in their code as a memory variable and it was not mdotted. It was an eye opener and since that time I always mdot where needed.
>
>you just never know when someone is going add a field/column to a table that is also used in the code as a variable. Sure, Hungarian naming conventions can reduce the potential for the error, but why take the chance.

Agreed, but some on this site argue completely against it, despite Calvin Hsia explaining how he even improved it. I am not interested in the stupid arguments of childish individuals, but actual evidence based science and the freedom from harassment to promote science.