RE: Month, day, year fields

In 1995 I switched from three fields to a true date.  I certainly would
encourge you to use true dates.  The advantages far out weigh the initial
problems learning how to handle *LOVAL as default date, null values
(normally I do not allow nulls).  I normally use the default format of *mdy
rather than *iso or *usa.  This is because almost all dates ranges are in a
one to ten year span; a date of 01/01/1896 ought to be considered invalid in
most cases. I use *usa for birth dates, etc. where dates prior to 1940 would
be valid.

The date arithmetic is enough reason to make the change.

Go for it.

Don Tully
Tully Consulting LLC
920 996-0448


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx
Sent: Friday, September 24, 2004 2:58 PM
To: Midrange Systems Technical Discussion
Subject: Month, day, year fields


Is there any valid reason to design new files with these fields separated
out, in the physical?  Versus using a true date field?  The only
difficulty I see with a true date field is that you either have to learn
how to code a null indicator on your field, or use a default date.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.