>>>>The only way I have succeeded in doing this is to use the OLDVAL() function.
>>>>If the values compare equal then SETFLDSTATE back to unchanged. Valid() is where I do it but LostFocus() should work too I guess.
>>>>Hacker's warns that using SETFLDSTATE() does NOT prevent an update from taking place so when it comes time to write I use GETFLDSTATE(-1) to check for any changes, reverting if there are none.
>>>
>>>Thanks, this is what I am doing as well.
>>
>>Michel,
>>
>>Sorry to inform you that a bug causes that it will not work anymore in VFP7.0 for fields with a default value!
>>
>>The SETFLDSTATE() command does not work anymore on fields with a default value!
>>
>>
>>
>>Koos Veel.
>
>Koos,
>
>Might this not be a question of where (when, actually) the SETFLDSTATE() is issues?
>
>I don't argue that SETFLDSTATE() behavior has changed, but only that it may be that using it in a different place in code may now be necessary.
>
>Jim Nelson

Jim,

I don't think so; it is a bug.

Try from the command line to SETFLDSTATE() from 4 to 3 for a field with a default value after you just appended a record.

This is simply not working anymore.

It is very important that it does work for frameworks like Mere Mortals that uses this command to avoid the "Do you want to save changes?" message after you click the "New" button and then "Escape" right away.

Koos.