|
Our database contains date types that are *ISO.
The DDS for our interactive applications reference these fields and specify
DATFMT(*MDY) and MAPVAL('01/01/40 *BLANKS').
All of the dates in our files that are zero use 01/01/40 to distinguish zero
since this is the first date that is valid on *MDY. DFT keyword is used on
all PF's date fields as DFT('1940-01-01')
Problem is when displaying initial screen of a workstation program that has
fields referenced, we get date/timestamp error because the field does not
have the DFT in it, it has 0001-01-01, which cannot map to a *MDY field.
Is there a simple way to force these fields to 1940-01-01? Currently we are
identifying these programs and inserting code to initialize all of the
screen fields. This stinks.
Yes, this is a Y2K project.
Art Tostaine, Jr.
CCA, Inc.
Parlin, NJ 08859
+---
| 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
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.