Date Entry Problem for Period 1900 - 1930 (AREV Specific)
At 11 DEC 1998 11:50:40AM Paul Blankenship wrote:
Our medical database uses the patient's DOB to calculate age and ultimately choose the correct age weighted normal value for lab reports. How does one handle the problem of a DOB occuring between 1900 and 1930? The system assumes this interval belongs to the 21st century…
At 11 DEC 1998 12:20PM Terry Rainville wrote:
Unfortunatly its sounds like your system has a Y2K problem in that
programming was done based on a 2 Digit year instead of using
arevs internal format for dates.
Jan 1 1968 is considered 0
Jan 1 1930 is -13878
Jan 1 1999 is 11324
arev works on a numerical time line.
You will need someone to go over your system and fix Y2K
bugs inorder to fix this problem.
At 11 DEC 1998 12:46PM Richard Wilson wrote:
You will possibly need to change your prompts to allow
mm-dd-ccyy type of entry. If the edit mask on the prompt
doesnt get in the way you can enter 01-01-1929 and it may
just redisplay as 01-01-29
more details would be need for a firm answer. Also I dont
consider this being a y2k bug. Back in the late 70's we had
this problem with many employee type of items since lots of
people were in their 40's & 50's
At 11 DEC 1998 03:45PM Paul Blankenship wrote:
Actually, I didn't explain the problem very well. I have a date prompt in which I need to enter dates of birth in the interval of 1900 - 1930. Since the system assigns this interval to the 21st century, the resulting display will be 2000 - 2030. I have tried every date validation I can think of without success, i.e., entering something like 10101901 displays as 10/10/2001.
At 11 DEC 1998 04:41PM Richard Wilson wrote:
Check out the knowledge base there is an article
dealing with implied dates.
My copy show's the following on the top of the page
"Date Fields in Selects (TB#112)"
I cant give you the full path address, my printer ate
some of it.
Rev has a version of Iconv that was modified to handle
implied dates, it is addressed in the above article