This form was created freshly, NOT by using SAVE AS from another form. This problem started a considerable time after the form was initially created.

In some cases (not mine), this seems to be caused by Combobox or Spinner controls on Page 1 of a pageframe on the form. Please see Bruce Campbell's earlier replies.

>Hi Al,
>I've had a similar problem with VFP 5.0a under Win95 and have not figured it out yet. Did this form always behave this way or did it start some time after creation ? By chance did you "Save As" another form to create this one ?
>
>Carl Chambers
>
>>I have a misbehaving form. If I open it in the Form Designer, then close it immediately, it asks me if I want to save changes, even though no changes have been made.
>>
>>This form now is causing problems in my app. First, it caused VFP to "drop out" to the OS with no error message(s). Second try, it GPF'd VFP.
>>
>>I then re-opened the form, made tiny edits to all custom methods and saved it (idea was to force VFP to rebuild the object code for the methods in case some got corrupted). Rebuilt my app and ran it. Form now opens OK. However, when it is edited, it still asks to save even if no changes are made.
>>
>>Why not ignore this problem, you ask? The last time I did, the form (a different one) went seriously south on me and I lost it all (9-page pageframe, 170 fields, etc.)
>>
>>Is this a sign of incipient disaster in the form? If so, can anything be done? I'm happy digging in the .SCX/.SCT if that's what it takes.
>>
>>Environment: VFP 5.0a build 415, under NT 3.51 SP5