Re: Help !! Using Lov for DATE validation

From: lge <elkinsl_at_flash.net>
Date: 1997/06/03
Message-ID: <3394acef.83208916_at_news.flash.net>#1/1


jurij.modic_at_mf.sigov.mail.si (Jurij Modic) wrote:

<snip>

>>We are using the above property to validate an date entered into a non
>>base table (NBT) field with a format mask of DD-MON-RRRR.
>> .... [SNIP] ...
>
>Your format mask is invalid. It should be DD-MON-YYYY or DD-MON-RR.
>The first option will always solve the millenium related problems
>while the second is solving this problem only potentialy and not in
>all circumstances. So stick with the first model if you can.

[Quoted] Using four R's is valid. For Forms 4.5, we define the format mask as "MM/DD/RRRR". If the user enters all four digits of the year, it is taken "as is". On the other hand, if the user enters only two digits, the digits are assumed to be the year, and Forms will apply the RR logic. Using this approach, the user still enters 2 digits for the year as they always have. For those occasions that the RR rule does not apply, the user can type all four digits for the year and the RR logic does not kick in, and, they can enter a date such as "6/29/1939". The benefit is that in many cases the user can still get away with typing two digits and the RR assumption takes care of things; but, they aren't restricted to the RR rule -- they can still enter any date they want whether it conforms to the RR logic or not. Received on Tue Jun 03 1997 - 00:00:00 CEST

Original text of this message