Re: Dates and triggers.

["David Morris" <dmorris@xxxxxxxxxxxxx>]

Booth,

Invalid dates cannot be reformatted successfully.  We take our best guess, if 
the value is not a valid date, it is rejected and the original screen is 
redisplayed as it was sent.  It is similar to entering a "       3000" in an 
edited field defined as 7.2 and having it come back as "   3,000.00 ".  Where 
"3000.00000" is redisplayed in error.

David Morris

>>> <boothm@ibm.net> 07/31 8:19 PM >>>
I am curious how one can "reformat incorrect dates" successfully?  With
the discussion a few days ago about 03/03/03 and 07/11/01, etc, I was
thinking that correcting dates is now impossible, except at the entry
point.  btw, if the field is a date field, then you don't have to worry. 
It won't be accepted anyway.

In <s5c1c8f4.037@plumcreek.com>, on 07/31/98 
   at 01:38 PM, "David Morris" <dmorris@plumcreek.com> said:

>Data base experts,

>On files with triggers, it appears as if dates must be valid in the
>buffer before the trigger is fired.  We were hoping to be able to
>reformat dates entered in an invalid format in either the
>pre-update/write action.  The incorrectly formatted date never gets to
>the trigger.  A date or timestamp exception prevents the trigger from
>executing.  Is there any way around this?  We do not have control of
>every application to reformat the date before the trigger is fired.

>Thanks,

>David Morris

-- 
-----------------------------------------------------------
boothm@ibm.net 
Booth Martin
-----------------------------------------------------------


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---