World: r3wp

this ensures that years more than 10 ahead get changed

explicit 4 digits are not necessary?

but quick solution :)

Since we don't have control over the field .. users will enter 2 
digits sometimes

i mean user can enter 2025 explicitely. that gets 1925.

well, I see ... he made a mistake.

In my application .. you are not allowed to deal with dates too distant.

:)

this solution:

>> 24/10/55
== 24-Oct-1955
>> 24/10/54
== 24-Oct-2054

ok, than this is enough. but people get older in the future! (hopefully)

is considered "standard", but it doesn't look ideal for medicine 
applications

I would require users to enter four digits. Get them used to being 
precise.

sorry "we don't have control of the field..."

mmm.. so you have to guess. A bad situation.

Hey, living users won't have to worry about the next century!!

i would use grhams solution and feed what rebol sees back into the 
input-field. so user sees something is wrong.

Ladislav, how did you know the cut off date?

middle? 50 years?

ahh...

well, I think we need an adjustable window

adjustable window - you may put it to RAMBO as a request, but I am 
not sure if you succeed

would something in system/options be a big effort?

I thought RT wanted to get into medical applications :)

OK, try to put it there and let's see :-)

system/options sounds appropriate

currently it is -50 to 50 but even -100 to 0 isn't "safe" (ever heard 
anecdotes about inviting over 100 people to elementatry schools?)

I think it is importan if you get dates as strings, you dont know 
after the converion if it was 2 or 4 digits. makes the smartness 
of to-date useless, going back to self-made conversion. OTOH in most 
cases defaults are enough, but so are english month :)

main point may be, some dates cant be in the future, like being born.

110 - 0 should be enough

but impossible

it is more than 100

there are many centenarians around.

:-P

the Galapagos turtle that was said to have been brought back by Charles 
Darwin is over 160 years old now.

so, for vetinary applications, would have to adjust the date window 
even further.

maybe hexdates, going to 255? :)

your trouble is, that the window is only 100 years wide

so if you want it to start at -110, it can go to -10 maximum

Well, I think the vets can argue their own case,  I can work with 
a 100 year window.

this is not about computers, it is about the fact, that two-digit 
years can represent only 100 years, i.e. no "window trick" can give 
you more than 100 years

with all those extinctions that -10 window may be ok.. :(

If there is a 4 digit field, then birthdates pre last century would 
normally be added in 4 digits by most people.

Why don't you implement the window yourself with a parse rule? It 
wouldn't be difficult to parse the date yourself.

because although I can do it, someone else may not be able to do 
so.

I think, that we have successfully proven, that two digit dates are 
insufficient for human medicine regardless what window we choose

to-date/birth

but still, is a "24/Oct/05" a newly born or a 100 years old?

Either way congratulations are in order :)

:-))

to-date/newborn