>>>>Oh, well. Thanks to everyone who tried to help.
>>>>
>>>>Maybe I should report this to Microsoft as a bug (in their next beta).
>>>
>>>Tom,
>>>
>>>I don't think that this is a bug. For one thing, VFP passes all objects by reference, so when you add the @ you're really not doing anything. In this case, since VFP doesn't know anything about what the object is it evaluates the first element. Note that this is consistent with the way the TYPE() function works. Certainly, I wish that this wasn't the case, but it's been this way for so long, that I don't anticipate them making any changes.
>>>
>>>George
>>
>>Yes, but how can you send a property by reference to a function?
>>
>>Vlad
>
>My guess is that you'd send a reference to the object to the
>function and let it work on what every it needed to.
>
>Steve

Yes, this is one solution. The problem is that many developers have their own function libraries and they want to use them for VFP projects as well as for FP2.x applications they must maintain. Of course, the libraries may be converted as well, but usually you don't want to have 2 versions and for certain tasks, the old functions are exactly what you need.

Vlad