Re: Dates and triggers.

Tim,

We have many front end applications, and one single database application.  We 
have always allowed users to use date shorthand in interactive programs.  For 
example '731          ' is automatically reformated to ' 7/31/1998'.  We use 
this type of processing extensively.  It was previously implemented in our 
applications.  I attempted to move the code to our database I/O servers and 
uncovered this situation.  It is easy for us to implement this in the front end 
application, but in some cases those applications do not have access to our 
database definitions or formatting procedures.  This is the case for some web 
based entry programs, file utilities, ODBC, etc.  It is not a big problem, I 
just thought there might be a work around.

Thanks,

David Morris

>>> Tim Truax <truax@usaor.net> 07/31 3:44 PM >>>
Hi David,
I am curious?  Why don't you stop the invalid date right at the front end 
application, instead of assigning it as a database operation function? The 
triggers I have implemented were raw data handlers.   I am suprised to hear 
that there would be any date checking unless it was specifically written that 
way by a programmer.
Good luck
----
Tim & Dana Truax... and Caleb 4 years old.


David Morris wrote:

> 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


+---
| 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
+---