>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?

Hi Bob;
As usual, you have come up with a very interesting discusion topic and I have found it fascinating reading the thread so far. My approach is (as usual) just a little bit different. I try to think like a user and came up with a multi-level approach to saves.

First - with master database entries that are usually put in once and then edited I stick with a strict Save button approach on the theory that most often the user will not be filling in all the fields and can then save (using mouse or short cut) when they want to instead of having to get to a particular point.

Second - for daily data enty (in this case order processing) which comprises 90% of the data entry, I took the approach that most often, the user will want to complete all the fields. So, dividing entry into a header and detail lines, the first thing they enter is a header. Data is only saved after the first data line is saved unless the user hits the save button sooner. When it comes to detail lines, (and we are talking add mode here not editing) when the user gets to the end of a detail line and exits the last control two things happen automatically. The detail line is saved and if it is the first detail line the header is also saved. As well, if the user has indicated continuous entry, a new detail line is automatically inserted. This allows for continuous heads down entry without ever having to use the mouse or short-cut keys. Edit mode is strict Save button on header and detail lines with a check for changes before allowing the form to close or record pointers to move.

As for the wait window, I also use that but with a no wait clause so if the user isn't looking for it, they will seldom even see it but if they want confirmation they can look for it.

I like Bruce Campbell's approach of saving all the edits and I will be looking at that kind of approach in the future. There have also been some other interesting points brought up that I will have to keep in my interesting thoughts folder. TTYL

- Bruce -