Thanks for pinpointing the variables Alex. I agree with you about the lifehood of s/w, but I made the date increases for psychological reasons to the customers, who view 40 years from now as more of a lifetime than 10 yrs. This is really only applicable to lifetime subscriptions, and like you said... from the admin's standpoint, the s/w will be updated before the end date. I noticed also that if you go beyond 2038, it will set your end date as 1969. Not sure if this has to do with the unix epoch or not, but I've set my customers to expire on 2036 (far enough out). From that standpoint/limitation, it is a data limitation, because it forces you to keep you expire date within a certain timeframe which could be less than lifetime (or take the consequence of the s/w presenting the date at 1969 if you set your expiration entry beyond the epoch).