Re: [WSG] Standard for committing changes to a database?

2008-04-14 Thread James Jeffery
Let the user modify the data and submit any changes. Its how most applications work and its what the users are used to. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe:

Re: [WSG] Standard for committing changes to a database?

2008-04-11 Thread Joseph Ortenzi
who is your target audience? If they are basic desktop users and not technical, then you want to use language they understand rather than the technical language. Commit changes is too technical, and you should never mix the commits in any one view. I like the Save changes suggestion. by:

RE: [WSG] Standard for committing changes to a database?

2008-04-10 Thread Elizabeth Spiegel
Hi Jessica As a user, I am really annoyed by applications that don't work consistently - they're much harder to learn (at work I have to use one that labels the same tool a 'Power search' in one place and an 'Advanced search' in another). I would prefer to see a 'save changes' button (or

Re: [WSG] Standard for committing changes to a database?

2008-04-09 Thread Taco Fleur
Interesting; we're going through the same process here. There is talk about converting the view pages to editable pages that commit the changes right away. I'm completely against it. I think it will bring along with it lots of issues; - when you have text fields that are 20 in size, and the text