Ahh, the beauty of semi-ambiguous questions. You get multiple answers based on the responder's own experience and interpretation of the question. IAC, I think there was value of traveling down both forks of the road.

I have seen something similar to your experience myself, but it usually occurred when I open a form to modify, open something else on the form (DE, code snippet, etc.), then wind up closing the form without making a single change (not even a *reverted* change). Something inadvertently trips the modified flag. This has never annoyed me as I just move on past it.

>>PMFJI, but I've had the problem come up when a combo box has a default value stored to it during form init() or when the record pointer is moved. What I did was in the form init (and all record changes), when all the setup code was done I checked GetFldState(-1). If any field was 'changed' I issued a save. Klutzy but it solved the problem.
>
>Jumpers always welcome :) But I was referring to the design problem of opening a form (modi form) then immediately closing, but getting "Do you want to save..." message, when you haven't even touched anything. Occurs on "large" forms with pageframes only. Apparently a problem of complexity in a pjx, it becomes confused and thinks you've made design changes when you haven't. I think it might be fixed in 6...