Suman,
1st part of the solution would ofcourse be how the forms are designed
- to prevent the error itself.
If the error does happen, here aret eh things we have done with long
forms:
1. Display error as user moves from one field to the next and not on
Submission. This reduces the number of errors users have to deal with
2. In our case we created a hierarchy of errors - for instance if a
password field was left blank - then we throw and error that it was
blank and not that it did not have minimum characters and it did not
use a number etc.. so only 1 error
- AJ
On Jul 6, 2008, at 11:28 AM, Suman Paul wrote:
I with banking software.
For me things are bit different.
Inline error although is a god idea but most of the forms being large
and having constraint of showing maximum in one page kinda rules it
out.
Combine with it numerous validation error which might occur,
developers shy away from providing specific error messages and prefer
throwing generic and even in some cases technical error messages.
Any proven method how to show error in such situation?
Of course simplifying the form itself will solve lot of problem, but
yet we are left with lot of fields and more the field more the chance
of error.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=31032
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [EMAIL PROTECTED]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [EMAIL PROTECTED]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
