Thanks I'm doing fine. Sorry couldn't check the thread in more depth (work work work:). BTW thanks for note with C5. I though try to be aware of it sometimes totally forget about it might be a reason for C5 (VFP kindly reminds:)
Cetin

>Cetin,
>
>>m. is missing on the right side of expression < bg >
>>netdiff = withmdot - withoutm
>>Shouldn't it be :
>>netdiff = m.withmdot - m.withoutm
>
>This is a great catch, Cetin. It explains why in the original instances netdiff evaluates to zero.
>
>>Honestly this is my #1 reason to use m. whenever possible rather than speed. VFP can use anyname as memvar.
>
>No argument here. The question was, "Is using this notation always faster when dealing with internal object?" Given that it isn't always faster, and that the use can cause a C5, I think it's a good practice not to use it when dealing with internal object references.
>
>>Depending on table in use, mdot might catch up and even be much better than dotless version IMHO. I remember I showcased this with an exagarated table structure where it took ages for dotless version to complete. Include a property and things are worse :
>>this.myProperty
>>vs :
>>m.this.myProperty
>>
>>

>>o = Createobject('myTest')
>>m.o.doit()
>>
>>Define Class myTest As Line
>>  myProperty = 5
>>  Procedure doit
>>     Create Cursor This (myProperty i)
>>     Insert Into This Values (1)
>>     Select 0
>>     ? This.myProperty
>>     ? m.this.myProperty
>>Endproc
>>Enddefine
>>

>>PS: Using keywords as cursor/aliasnames is another story but say I already utilize 'update' command not making a difference between and alias and an objectname :)
>
>Thanks for the feedback, my friend. Hope all is well with you and yours.