Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Built-In Editing/Auditing of Input in Date Fields

IP.com Disclosure Number: IPCOM000099627D
Original Publication Date: 1990-Feb-01
Included in the Prior Art Database: 2005-Mar-15
Document File: 1 page(s) / 51K

Publishing Venue

IBM

Related People

Eisen, I: AUTHOR [+4]

Abstract

This article describes a method to automatically edit/ audit inputs from a NLS enabled date field. Any application which must support the input of user given dates will be able to function in a large number of countries and locations and support users that use different calendars and present the dates for those calendars in various forms and not have to worry about validation. All of the Editing and Auditing complexities are totally hidden from the application.

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

Built-In Editing/Auditing of Input in Date Fields

       This article describes a method to automatically edit/
audit inputs from a NLS enabled date field. Any application which
must support the input of user given dates will be able to function
in a large number of countries and locations and support users that
use different calendars and present the dates for those calendars in
various forms and not have to worry about validation. All of the
Editing and Auditing complexities are totally hidden from the
application.

      A means to automatically validate a user input Date to see that
the date is correct for the calendar chosen by the user is required.
For example, the date February 29, 1989 could be input by a user who
prefers the Gregorian calendar. This date is not valid (even though
February 29th was valid in 1988), so the user should be notified of
an error.  This concept can be extended to any calendar (e.g.,
Gregorian, Islamic, Julian, etc.), and to the presentation of the
date in any format which the user has specified in any sequence
(i.e., era, month, year, day, weekday). The Editing/Auditing should
be built into the Date Control and take into account cultural
preferences, such as Calendar type (e.g., Gregorian, Islamic, Julian,
etc.), Era identifier (e.g., AD, Showa), start of year (e.g., January
1st, March 1st), weekstart, daystart, time zone, and daylight savings
rule. The user should be immediately notified of any errors found in
the Date field.

 ...