>>I still do not understand tha use case.
>>For example, you put in table default value expression for primary key field. When you use APPEND BLANK command, new primary key generated automatically and put into the field value. I do not understand why you want to mark it as it is not changed. Is it not enough just clearing the field value?
>
>[Christian]
>The reason I do this is, that when the user closes the screen or attempts to move to another record, I check for changes with the GETFLDSTATE() function.
>In most programs, when you click on the new button, you get a new record, or document or worksheet, but when you do not make any changes as user, you won't be prompted for saving or discarding changes when you close the application/document/worksheet etc.
>From the user's standpoint, no changes have been done. From the program's standpoint, some fields may be changed. These should not be detected in GetFldState().
>(Using another check than GETFLDSTATE for changes is much more work and time intensive.)
>

Ok I see now what you meant. This is depended on how your interface is designed.
In my application I based each form control on the custom class in the class library. In the methods InteractiveChange I put a call of the form method (forms are also a class) that indicates that data are changed. This way I never required to use GetFldState() to track if something changed.

Anyway, the question you asked here is very interesting and probably it is good idea to post a wish to the Visual FoxPro .next (Toledo) wish list (accessible from the documents section here). It would be good if APPEND or INSERT will have an option to do not mark record as changed by default values for field. In VFP6 it was ok when using on of these commands...

HTH.