how to make DEFAULT CENTURY be the current century

[Glenn J. Koster, Sr.]

Kent wrote:

> Glenn is not considering how much data will be dealt with on both 
> sides of Jan 1 2000.

Ah, but I am - that's why I think that the "INPUT CENTURY" is a good
addition.  It requires a modification to the original database and
effectively allows date windowing.  It requires a conscious choice by
the developer to be made. 

Perhaps what is also needed is an "OUTPUT CENTURY" to handle the output
dates for those 6-digit dates that are still in the data...

However, not all applications need to have any century other than the
current (default) century.  Hence, for those applications the system
date is what should be used so that no changes are needed on 12-31-99.

Glenn

-- 
 ______________
|  Navigators  | Under contract to Hewlett-Packard ISG (Greeley, CO)
|     |)       |
|     | )      | Glenn J. Koster, Sr.             gkoster@mbsnav.com 
|     |  )     | Managed Business Solutions    http://www.mbsnav.com 
|     |   )    | 214 S. College, Suite 201              970 350-5337 
|     |----    | Fort Collins, CO  80524                970 224-1016 
| ============ |  
| \__________/ |  
|   of Change  | aka:  MichiTex@aol.com
|______________| home: http://members.aol.com/MichiTex
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.