Fabio,

This is not bug, it's designe behavior.
Why?
1) You can't send field as reference.
2) If you not specify m. then field has priority, if exist.

Look at help to "Access to Variables"

MartinJ


>Previous issue Thread #950993
>
>Bug/Issue : 2 of 27
>
>TITLE: Bug: call by Reference search in the list of the fields
>
>VERSION: 09.00.0000.1720 and previous
>
>STEPS TO REPRODUCE:
>

>CLOSE DATABASES ALL
>CLEAR
>CREATE CURSOR pipe (anyName I)
>SCATTER MEMVAR
>ON ERROR ?? MESSAGE()
>? 'Call is ',BLA(@anyName)
>? 'Call is ',BLA(@m.anyName)
>ON ERROR
>USE
>
>PROCEDURE BLA (p1)
>	RETURN 'ok'
>ENDPROC
>

>
>
>OBSERVED BEHAVIOR:
>When the call by reference is made without the prefixed one m., VFP explores the list of the fields and if a field with the same name exists, it generates an error.
>
>EXPECTED BEHAVIOR:
>VFP does not have to explore the list of the fields when a call by Reference is done ( like on macro substitution )