DH>> This is a good component of writing software that lasts longer than
 DH>> a thousand years, but suppose I have 'Century 2000' in my configs when
 DH>> the rollover happens. How will Max interpret existing files dated
 DH>> 02/25/97? Wouldn't it think it was 2097? There needs to be some
(to DH)  The key here is that Maximus does not need to interpret *existing* 
dates.  Dates in the filesystem are unambiguous, as are dates entered by the 
user that Maximus has already converted.
The problem is how to interpret dates entered by users.
 SH>> there are people who are born  pre-1950, so there's a problem, so
 SH>> you'd have to set it for about 20
 DC> How about between 80 and 99? Very few people born between 1880/1899 will
The DOB routines already accept four-digit dates (see \max\m\chgdob.mex), so 
I don't think this will be a problem.  Even an explicit specification of a 
"pivot" date is unnecessary; a pivot of the current year plus 50 should be 
sufficient for most dates that are entered by the user.
---
---------------