Browse Prior Art Database

Preserving Data Validation

IP.com Disclosure Number: IPCOM000120682D
Original Publication Date: 1991-May-01
Included in the Prior Art Database: 2005-Apr-02
Document File: 1 page(s) / 58K

Publishing Venue

IBM

Related People

Weber, OW: AUTHOR

Abstract

Described is a mechanism to preserve valid data in a date field, even when the user overrides it with invalid data. There needs to be a consistent convention for performing data validation of user-entered date fields, which will allow the user to proceed successfully, even in the event of unsuccessful data validation. This article describes the invention of a convention that will preserve the data validation, and yet help the user to proceed.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 60% of the total text.

Preserving Data Validation

      Described is a mechanism to preserve valid data in a date
field, even when the user overrides it with invalid data. There needs
to be a consistent convention for performing data validation of
user-entered date fields, which will allow the user to proceed
successfully, even in the event of unsuccessful data validation.
This article describes the invention of a convention that will
preserve the data validation, and yet help the user to proceed.

      The problem occurs when a user enters data in a date field with
the format: "10/7/90".  The user may want to enter this date, but
suppose, instead, he enters "1O/7/90", where he accidentally entered
a capital letter "O" instead of zero for the last digit of the month
field.  The EUI (End User Interface) performs data validation of the
user's input, and an error message is displayed, telling the user
something to the effect of an input validation error occurred on the
date field, or there is an illegal character in the date field.  The
user then studies the date, but the help from the EUI is insufficient
for enabling the user to correct the problem.  He may even try
entering the same data again, and he receives the same message again,
so he gets frustrated and he cancels that part of the application.
Clearly, the user is not happy.

      The solution is to provide a new mechanism for correcting this
problem in the application EUI, by saving the old data from the field
before the u...