>I was looking at an application yesterday that was very annoying. Everytime you saved a data change a wait window came up with "Your data has been saved - press any key to continue".
>
>It got me thinking "why do we need a save button at all?" When I fill out a physical form I don't have to save it. It is saved by virtue of having filled it out. So why do we require users to 'SAVE'?
>
>I'd like to think there is an elegant metaphor for intuitively saving data without asking the user to do it.
>
>If you look at some of the forms that change settings in Win95 or IE4 etc. You don't have to save. You can cancel, but the boxes you check etc are saved automatically.
>
>Does anyone build forms that save data without explicitly having a save button?

I'm of the opinion that we need a save button, mainly for the reasons already given. However, the interface you saw does have a couple of problems.

First is the use of the WAIT WINDOW. Too easy for the user to miss. If I require the user to respond, I always use MESSAGEBOX.

Second, there is no reason for the user to press a key at that point. A WAIT WINDOW with a timeout of 2 seconds should be sufficient.