Hi Terry,

Thanks for the reply. It looks like this is going to be one of those "best practices" that I'm going to have to follow from now on.

Mike


>Mike
>
>I think this is a fairly old chesnut that pops up quite often. I figured this one out years ago. Now I always set a memvar to the form property if I'm to use it in any table searching, including SQL.
>
>Terry
>
>>Hi Greg,
>>
>>Thanks for the reply. On the one hand I'm "happy" to know that others have found this to be an issue. On the other hand, I wonder if the VFP team knows about it and fixed it. As I've said, I cannot make it happen on any computer that I have access to! Kinda makes using WITH/ENDWITH limited. Now I've got to go my code looking for all instances where I did this sort of thing and change it :(
>>
>>Regards,
>>
>>Mike
>>
>>
>>>I have experienced the same problem with version 7 (have not tested with v8 or v9). Found the same problem with the INSERT INTO command as well. It would not always "show up" as an error. As a workaround, I assigned a memvar to the .property reference or used the entire path (thisform.property).