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: http://webstandardsgroup.org/j
eview before you save
something
awful.
Elizabeth
Web editor
www.spiegelweb.com.au
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Jessica Enders
Sent: Thursday, 10 April 2008 11:38 AM
To: wsg@webstandardsgroup.org
Subject: [WSG] Standard for &
Thursday, 10 April 2008 11:38 AM
To: wsg@webstandardsgroup.org
Subject: [WSG] Standard for "committing" changes to a database?
Hi everyone
I am currently reviewing a desktop application that involves mostly viewing
and changing records in a database (via a nice GUI front end).
In some pl
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
Hi everyone
I am currently reviewing a desktop application that involves mostly
viewing and changing records in a database (via a nice GUI front end).
In some places, changes are "committed" as soon as you enter them, a
bit like how Microsoft Access operates. In other places, the user has
