>>>>>>>I've been "officially" retired for several years now, although I take occasional assignments. I have never been busier... :-)
>>>>>>Hrm... it might be interesting to see if there arises a situation where VFP programmers coming out of retirement -- much like how a number of retired COBOL programmers that were brought out of retirement to deal with the Y2k crisis.
>>>>>>Personally I've some feeling of dread about 2038...
>>>>>
>>>>>Is there any particular date-related thing that hits the ceiling then?
>>>>End of 32-bit Unix time (seconds since UT 1970.01.01 00:00:00 kept in 32-bit two's complement integer goes negative in 2038). Anything using same representation will end up with same or similar problem.
>>>
>>>By then, I'll have forgotten about it at least 32767 times, or -1...
>>
>>You are still thinking in 16 bits are you ?
>
>Memory saving... my forget counter is 16 bit. When it rolls over, I just increase the forgotten things counter by one (i.e. the number of things I forgot that I forgot).

You almost sound like what I remember of the IBM-PC BIOS (software) clock -- when the time rolls past 23:59:59 it sets an internal flag so that the next time you performed a call to get the time it would increment the day and clear the flag. If you happened to leave your computer on for several days (and didn't perform any call to retrieve the time or date), it would only catch the first date change and miss subsequent ones. I vaguely recall that this bug was "fixed" in a version of DOS (which periodically checked the time/date).

I suppose it could be worse -- for example your memory consisting of WOM (write-only memory) or WMRN (write many, read none)...
Apparently many people seem to be annoyed by my tendency to leave my auditory subsystem in "pass-thru" mode that bypasses cognitive functions.