>...
>>My conclusion on the topic is that you'd better find another way of avoiding the fieldname/variable conflict because realy if you need to know all of this in order to create some code, you should realise that No-one is going to be able to adhere to this standard.
>
>Why not? All one would have to do is to start typing m. in front of your variable references. That's all you need to do, and if you'd start doing it today for any new code that you'd write, your future programs would not create/introduce any further ambiguities.

Why not? Because our coding convention is such and I won't allow for a change that has no merit and would be full of loopholes just as the code on VFPx shows. Its easier to code without mdot than force mdot everwhere where needed. That is why.

>*
>Otherwise, what is your convention for naming variables? I missed that, if you posted it before.
>*

Prefix with type, then camelcase the rest of the variable name, like

nT, cPatientName, lVisible, etc