>I stumbled into this in trying to be able to have a changelog of form changes; I was first relying on this field to be updated to be able to record a change to the form control. All seemed to be working until I came across the anomoloy described above. I also noticed after this, that if you go in to a form (via USE) and REPLACE ALL timestamp WITH 0 and then close and open the form (MODIFY FORM...), and then close and subsequently USE the form, you will notice the timestamp is reset on the first and last records and the form record (and any cursor records), but all other control records remain at zero. This all happens without saving the form in the MODIF FORM.

I was using a similar trick in project manager - if I wasn't sure it would compile properly (in FPD2.6) I'd just blank the timestamps and objcode in the .pjx, and recompiled. Worked a charm and circumvented any bad filedates (the network we had back then suffered from clocks on various cheap machines going off unpredictably).

Just tried what you said on a vcx - and if I didn't save it, the timestamp remained blank in all records. If I just saved it, then it'd set the timestamp on records 2 and 3. Then I moved one button - and sure enough, its timestamp was refreshed.