ORA 01839: Forms 5.0 Y2K bug

Can't find anything about this in newsgroups, Metalink, or Technet.

GET_ITEM_PROPERTY(:block.item, DATABASE_VALUE) causes ORA-01839

   ("date not valid for month specified") errors when the returned    date is FEB 29, 2000.
NOTE: it works fine for any other date (that I've tested).

[Quoted] The failure occurs when accessing FEB 29, 2000 in an assignment to

   a date variable:
   dt := GET_ITEM_PROPERTY(:block.item, DATABASE_VALUE);

The failure occurs when accessing FEB 29, 2000 in an argument to

   a date function:
   dt := TO_DATE(GET_ITEM_PROPERTY(:block.item, DATABASE_VALUE));    str := TO_CHAR(GET_ITEM_PROPERTY(:block.item, DATABASE_VALUE));

The failure does not occur inside a simple MESSAGE statement:

   message(GET_ITEM_PROPERTY(:block.item, DATABASE_VALUE));

This method was used in an ON_UPDATE trigger to compare the original

   date value (prior to any updates) to the current one.    IF :block.item = GET_ITEM_PROPERTY(:block.item, DATABASE_VALUE) THEN

Hope this may save a few people some time, next year, right around the end of February...

Rich

Claim: The company that owns this intellectual information has okay'd

   my posting of it. The information itself and any opinions stated    here are created by myself and are not warrented or verified by any    other person or organization. Use this information at your own risk.

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Mon Jun 14 1999 - 15:34:36 CEST