>>- There a certain situations were you cannot work with m. (e.g. macros)
>
>Yes, but
>a) VFP formal design, it is a lot far away from the correctness,
>then m. rules it is not strong rule:
>rule it is : when you want to use a memvar, and language it is ambiguous
>then you have to use m.:
>- on macro VFP uses only memvars ( then the context it is not ambiguous )
>and this program are within VFPuniverseWithMDot because
>a program with &m.memvarname where m. it is the prefix is out of VFPUniverse.

>True cause it is a little bad design:
>

>clear
>memvarname='1'
>
>&m.memvarname && <== this is a incorrect syntax program
>m='? '
>&m.memvarname
>&m.m			&& this is interesting use m memvar two times !
>

Again, you did not dissapoint me. Interesting...

>>OTOH, if I´ve got to choose between the way the majority uses m. (as outlined on the wiki) or the way you use to emply, I´d choose the latter. IMO the wiki topic is an idiotic way of coding having to learn stupid rules when to use them or not, from at least an outsiders point of view.
>>If you want to be consistent then use them in all cases possible and not having stupid rules when not using them because there can be no confusion.

>Not to debit things to me that I have not never said.
>I say to always use m., and I always use it.

I was not directly talking to you here, but to VFP developers in general.

>>No then, either use them religiously or don´t use them at all, unless forced to (to avoid referincing problem).

>>BTW, for the lurkers, who like to think to avoid the referencing of a field using m.:
>>Do you realize if you really want to avoid this 100%, you´ll have to code.

>>m.MyObject.Myproperty ISO MyObject.MyProperty
>>
>>m.THIS.MyProperty ISO THIS.MyProperty
>>
>>m.THISFORM.MyProperty ISO THISFORM.MyProperty ?????

>Bravo, you have correctly deducted! I did not doubt that you can.

>>Please look at you source code and tell honestly you did this consistently...

>If you look into my source code, you see only, say 1000% this coding form!

I know yours will (as the line above was not directed at you), but as for the far majority talking using m., I´m not all that sure.

>

> m.blabla.blublu
> m.thisformset
>....
>

>Nothing of strange for me. Therefore it must be made.

>>I´ve seen Fabio do this and beeing burned for this. But you might give him more credit for doing this way.

Again I was talking to the lurkers. Not to you. Just wanted to point out that if you (not Fabio, but the lurker) use m. you´d better do it the Fabio way, or not at all.

Walter,