>Mike,
>
>>It is simply obvious that if you have some rules in place that limit your exposure to mdot issues, that you are 1) less experienced with dealing with them and 2) limiting your environment.
>
>I don't quite understand what experience has to do with. FYI, I did use mdot in the FP2.x days but went away from it. I know all the circumstances where to use and not to use mdot. I know all known technical details surrounding the mdot. Further I know that there are lots of less experienced or less professional people fall into the trap of not using mdot when they should. How does this make me any less experienced than anybody using mdot ??
>
>My point is: Personally I don't see any reasons to use mdot in my projects unless there is absolute need to, because:
>
>- Collisions of fieldnames and variables are avoided.
>- It is my personal preference not too use it.
>
>And that is the bottom line. You can agree with it or not, but that is the way I've been doing it since I started using VFP.

Walter,

The only place I use the mdot convention is in the command window because Intellisense kicks in.

The only reason for naming conventions is to make the code more readable.