>>In addition to Trey's and Rich's suggestion, if you have a field name with the same name as your variable VFP will use the field value instead of the variable value.
>>
>>Barbara
>
>Unless you specify m.varname. I always specify m. or alias. in any position of a command where there's possible ambiguity. Doesn't everyone? :)

And now we need to define 'possible ambiguity'. I got bit by this recently with a variable used in a purchased framework. Took HOURS to track it down deep in the base application object. Discovered one of the few places the author DIDN'T use a variable named like "MyVarLoadTheFormInitRightHereToday", but used a simple 4-char variable - which exactly matched a field of mine with a different type() value.