>A FAQ on this would be nice Fabio...
>

I put it in the list of the jobs to do.

Fabio

>
>>>Hi Fabio
>>>
>>>>If you want to use a variable you "must" to use "m.",
>>>>otherwise you will keep on challenging the fate
>>>
>>>I generally have the habit to name variables with l for LOCAL, etc. and field names always start with the type of field, c, n, etc. I had use a precreated class, but learning from this I have renamed all vars to have a l at the start and also put in a LOCAL line at the top of the code
>>>
>>>
>>>>datasession is not a object, it is an container of objects.
>>>>
>>>>If VFP hide the field, how do you can to use a cursor ?
>>>
>>>Just for arguments sake, then why did & macro work?
>>
>>because, on macro, VFP use variable only,
>>and you cannot to put a m. prefix.
>>

>>x="? 'ciao'"
>>&x
>>* error
>>&m.x
>>

>>
>>Another implicit variable are AXXX() array functions
>>

>>CREATE CURSOR cc (aa i)
>>DIMENSION aa[1]
>>* field
>>? aa
>>* array
>>? aa[1]
>>* array
>>? m.aa
>>* array
>>? ALEN(m.aa)
>>* array
>>? ALEN(aa)
>>

>>
>>
>>
>>m. skip datasession search:
>>

>>CREATE CURSOR m (m i)
>>* error
>>? m.m
>>* field
>>? m
>>SELECT 0
>>* ERROR
>>? m
>>

>>
>>I can continue with other exceptions...