>>>>I believe in 2.6 valid didn't run unless that value in the object actually changed. I know in a browse you could use the :F to force valid to fire every time.
>>>>
>>>>Is this true of VFP, or does valid ALWAYS fire when moving off a object?
>>>>
>>>>BOb
>>>
>>>Only partly true in 2.6. In 2.6, the valid for a BROWSE column didn't fire unless the user made a change, unless you defined the column using :F (force validation). Valid always fired on leaving a GET, whether or not a change was made.
>>
>>One more distinction: Valid in 2.6 didn't fire if user pressed ESCape, now we have to mess around with LastKey() to check for it.
>
>That's funny ... I always had to check LASTKEY() for Escape in 2.6. Is it possible you're thinking of an earlier version?

FPD2.6a, just jumped out to try. I wrote a routine with a simple one get with a valid which displays a message and returns .f. and doesn't care about LastKey(). Ran it, and pressed ESC right on, and the valid never fired, and Read terminated.